compatibility
3 TopicsAppCompat with MSIX
Hi, I'm repackaging some (very) old apps in MSIX, and I'm facing a situation where I need to enable some app compatibility shims. I've tried doing this with the `registry.dat` registry hive, but it doesn't seem to work. I think I've heard something about using SDB in a MSIX package once, but I might be imagining things. Right now I've resorted to using an ImportRedirectionTable and a redirection DLL, but this only works for simple cases like Windows version lie. It would be amazing if there was a way to use an SDB inside a MSIX, but if the registry option could work, that'll do too. Did anybody manage to make this work? Thanks!154Views0likes1CommentCan you redirect the -UseWindowsPowerShell temp path in a session when running import-module?
Hi All, I'm using PS7 and calling a bunch of modules. To get Microsoft.Online.SharePoint.PowerShell to import correctly in PS7, I need to use the switch -useWindowsPowerShell. Without restrictions this is all fine. Using Constrained Language Mode, WDAC blocks the module on import in PS7, it'll import in PS5 without any changes. Looking at the event viewer its due to the proxy being setup in the user's appdata temp folder. Is there a process to modify the location of the proxy being created in the current session? It'd be great to redirect it to a whitelisted location for execution to avoid the issue. Whitelisting the temp folder for users isn't an option. Thanks!263Views0likes0CommentsWindows 10 Preview Build 17692 application compatibility.
Some applications do not work correctly in Build 17692. Some applications cause huge UI lag or fail to open, sometimes user has to end the problematic application in task manager. Previous builds have no problems with this bug. More information here, also applies to all Windows 10 versions Build 17692: https://techcommunity.microsoft.com/t5/Windows-Server-Insiders/Windows-Server-2019-Preview-Build-17692-application/m-p/2063991KViews0likes0Comments