Filesystem permission issue after 5.2 Beta 8 with MSIX installations.
Opened this issue · 4 comments
I'm opening this issue to track the state of this situation and to discuss the efficient workarounds.
I've seen that people have encountered an issue that prevents editing bitwig.jar in C:\Program Files\WindowsApps\Bitwig.Studio.Beta_<version_number>_x64_<hash>\ folder after 5.2 Beta 8 comes with MSIX installation method.
I wanted to test it with a Windows VM. I've changed WindowsApps folder ownership from NT SERVICE\TrustedInstaller to Everyone fixed this issue on my end.
This change may cause instability among Windows Store applications, although I haven't encountered any. In such cases, you can revert the ownership. No matter what, use at your own risk!
Here is the steps to workaround this issue on my end:
Screencast.from.2024-06-22.03-13-01.webm
If that's not working somehow, you can use a 3rd party tool like iobit unclocker or lockhunter to workaround this issue.
Edit: Using TakeOwnershipPro looks like the best option for now.
It looks like MSIX is like Flatpak for Windows, huh?
I tried the method in the video, everything is unlocked except the bitwig folder which gives an error, iobit gives me a blue screen, and lockhunter can't unlock it...
Someone in the same situation?
I tried the method in the video, everything is unlocked except the bitwig folder which gives an error, iobit gives me a blue screen, and lockhunter can't unlock it...
Someone in the same situation?
Someone from the community mentioned that s/he solved the problem with a 3rd party program called "TakeOwnershipPro". You can try to give it a shot.
It worked! thanks for replying!