microsoft / PowerToys

Windows system utilities to maximize productivity
MIT License
111.52k stars 6.56k forks source link

Error when installing new 0.68.1.0 #24631

Closed KidCe closed 1 year ago

KidCe commented 1 year ago

Microsoft PowerToys version

0.68.1

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

General

Steps to reproduce

After i installed the update 0.68.1 i get a Error Window with following content:

Version: 0.68.1.0
OS Version: Microsoft Windows NT 10.0.22621.0
IntPtr Length: 8
x64: True
Date: 07.03.2023 22:31:47
Exception:
System.UnauthorizedAccessException: Access to the path 'C:\Users\NKits\AppData\Local\Microsoft\PowerToys\PowerToys Run\Settings\PowerToysRunSettings.json' is denied.
   at System.IO.FileSystem.DeleteFile(String fullPath)
   at System.IO.Abstractions.FileWrapper.Delete(String path)
   at Wox.Infrastructure.Storage.JsonStorage`1.Load()
   at PowerLauncher.ViewModel.SettingWindowViewModel..ctor()
   at PowerLauncher.App.<>c__DisplayClass19_0.<OnStartup>b__0()
   at Wox.Infrastructure.Stopwatch.Normal(String message, Action action)
   at PowerLauncher.App.OnStartup(Object sender, StartupEventArgs e)
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

In the past i had Powertoys installed over the github installer. After i got this error the first time i deinstalled it, and reinstalled the 0.68.0 over Microsoft Store. I immediately got update notification for 0.68.1 and tried to update again, but the same thing happens.

PowerToysReport_2023-03-07-22-34-04.zip

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Other Software

No response

davidegiacometti commented 1 year ago

/dup #14840

microsoft-github-policy-service[bot] commented 1 year ago

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!