The Store version of OneCommander has some limitations compared to the standalone versions because it runs under some Microsoft Store constraints

• Operations on files in AppData and some system folders is limited for Store apps
• Per-operation elevation is not permitted - ex: copying into a folder without access will show UAC prompt but will fail, so elevating the OneCommander itself is the only way (Ctrl+Shift+F12) but not recommended
• There might be additional security permissions limitations due to permission bugs in packaged apps (a few users have reported that opening Office files would fail with permissions error)
• Always one or two versions behind the standalone versions due to time it takes to pass Store certification and potential delay for managing critical updates
• Microsoft account is required to purchase Pro license for the Microsoft Store version
• Reported issues with setting/changing default file associations
• No volume licensing option or company licenses