This is nearly identical to recent thread by Kippies titled "Kernel32.GetCurrentPackageFullName (15700)".
When starting from:
- Start > Apps
- %localappdata%\Microsoft\WindowsApps\PointPlanck.FileBot_49ex9gnthnt12\filebot.exe (Obviously had to take ownership of the folder first)
Windows cannot access the specified device, path or file.
If I start the product directly (from filebot.exe or filebot.launcher.exe):
It starts fine, I can edit configurations but when I go to rename files I get this error:
Which I understand is due to UWP app licensing - It must be started correctly as a true UWP app, not win32.
Command prompt just gives "Access is denied." when run FILEBOT.
My Box: Windows 10 1803, out of the box antivirus.
What I have tried:
- Another user on the same machine works - I would very much like to avoid having to re-configure all my settings of course
- Uninstalled via installed apps, then reinstalled. Before the uninstall I used the REPAIR and RESET options for the app. I also went as far as using VoidTools Everything search to find all left over drive traces of FILEBOT and removing them before reinstalling. Same for Registry entries
- Took ownership of the filebot Program Files folder and added EVERYONE to full permissions.
- Reset windows store in every way I could find on MS site. (My other apps run ok)
- Windows store diagnostics app said my Internet Explorer history folder was in a non standard location so I let it reset back to C: drive. This did not help, so I went on to clear all IE related history/temp files with both IE options and CCleaner
- When I run PROCMON there IS still a single ACCESS DENIED error by SVCHOST.EXE for this folder: %localappdata\Microsoft\Windows\History\Low\History.IE5, so I suppose that could still be related. When I deleted that folder (after taking ownership) filebot gave a DIFFERENT error during start that I didnt capture (something like could not find file or once it may have been invalid parameter), but as soon as I ran IE again to have it recreate the folder, the old error came back. (And ACCESS DENIED still shows up in PROCMON, but I cant imagine IE would fail to re-create the folder incorrectly) Perhaps the error happens for everyone?
- My cat had a good idea, but after I fed him it still gave the same error.