Must be yeah. I have folder with my old windows install on my internal SSD after the repair install, and it wont let me delete it due to not having the correct permissions, even though I am the admin. Even after going into the properties of the folder and giving all the user options full access...
That would be a good fix for the taskbar specifically, but that still leaves the light on my front panel restoring to its obnoxious default strobe pattern upon restart.
Disabling all of those apps from running on startup didn't fix the issue sadly.
I completely removed windhawk using Revo previously, and then re-installed it after seeing that deleting it didn't solve the issue. Also, according to this:
Windhawk shouldn't be able to cause any permanent issues...
One of the things I tried before making this thread was creating and logging into a new admin account and making settings changes, but it behaved the same as my actual account.
I havent done any manual mods to my system files as far as I can remember. I did have to disable bitlocker and safe boot to get my Linux Windows dual boot to work, but the issue Im having now didn't start until way after that so I doubt it's directly related. I'm in the process of doing a repair...
So I watched that video and at the end it said to double press esc if the first method didn't work. Doing this immediately made the bar jump to 77%, and then 100%. After it had completed the process, I restarted, but no luck. The issue persists.
Sorry yes, it was and is currently stuck at 62.3% If it is still working away then Ill probably just let it run, so long as it won't take multiple hours...
Not sure if I'm just being impatient, but I restarted and reran the command, it got to 61.3%, and then completely stopped for over 5 minutes. Decided to close the terminal and retry, and now the command wont even start to work, with it stuck at the point before the progress bar displays. The...
According to the output of that command, "The component store is repairable".
I wasn't sure if the command was supposed to repair automatically, so I reran it to see the output, and it was the same.