New
#1
Most apps and start menu won't work. Error 0xc0000022
I really don't know what could be causing this, but it has something to do with corrupt Windows files. This morning before any of this happened my computer was stuck on a black screen on startup with nothing but eternally spinning white dots. That was fixed by booting in recovery mode.
Now I can log in but almost all of my apps fail to start, showing "The application was unable to start correctly (0xc0000022). Click OK to close the application." The start menu, search bar, and message window simply can't be clicked. It would be easier to list the programs that do work - Chrome (thankfully), iTunes, Notepad, command prompt, powershell, other simple programs.
I'm pretty computer savvy but I'm still stumped. Here's what I've tried:
- Running sfc /scannow. Windows Resource Protection found corrupt files but was unable to fix some of them. An excerpt from the log:
Code:2017-08-28 23:29:51, Info CSI 000061f9 [SR] Cannot repair member file [l:18]'Command Prompt.lnk' of Microsoft-Windows-CommandPrompt-Shortcut, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked 2017-08-28 23:29:51, Info CSI 000061fa [SR] Cannot repair member file [l:17]'Fax Recipient.lnk' of Microsoft-Windows-Fax-Client-Applications, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked 2017-08-28 23:29:51, Info CSI 000061fb [SR] Cannot repair member file [l:17]'Shows Desktop.lnk' of Microsoft-Windows-explorer-shortcuts, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked 2017-08-28 23:29:51, Info CSI 000061fc [SR] Cannot repair member file [l:28]'01a - Windows PowerShell.lnk' of Microsoft-Windows-explorer-shortcuts, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
- Reinstalling Windows Apps in Powershell
- Creating a new user. The welcome tour thing crashed my computer due to the same error.
- Repairing my installations of Visual C++ Redistributable 2012 through 2015
- Running Process Monitor. That crashes too.
- Attempting to use Windows Troubleshooting to repair my installation. No change.
- Enabling Windows feature ''DirectPlay" under "Legacy Components"
If anyone has any other ideas I would love suggestions. Other people have experienced this problem, it seems, but only in limited scope. Just a few programs. I realize that reinstalling Windows will probably fix it, but I just did that a couple months ago and don't want to reinstall everything.
Quote