Windows 10: Chrome not opening after a system restore on Windows PC [Fix]

​

System Restore is one of the best ways to resolve system failures and other issues. However, we noticed that Chrome was not opening after a system restore. Although we can see the Chrome application installed on our computer, it just doesn’t open when we try to use it. In this post, we will see what to do […]

This article Chrome not opening after a system restore on Windows PC [Fix] first appeared on TheWindowsClub.com.

read more...

 

Chrome not opening after System Restore

This PC is running Winver 1909 (OS Build 18363.1082)

The original problem which led to a System Restore on my machine was an Application Error when opening Settings and attempting to use the System control. Initially, Restart appeared to fix it, but it recurred later

From the Event Log:
Application pop-up: SystemSettings.exe - Application Error : The exception unknown software exception (0x40000015) occurred in the application at location 0x00007FFB0BAFAE72.
Click on OK to terminate the program

Searching led to:
How to Fix Unknown Software Exception 0x40000015 Error on Windows?

From there it says:
The 0x40000015 Unknown Software Exception error might show up when using any program. The main reasons that trigger the error:
§ corrupted system files;
§ incomplete installation of software;
§ updates installation problems;
§ incorrect uninstall;
§ accidental removal or replacement of Windows registry

It was decided to Restore the system to a known good point in time – in this case, 2 days previous.

After performing the System Restore, was unable to open Chrome Browser – click on it and it does nothing, whether from Start, Task bar or directly opening executable.

The fix was to download the ChromeSetup (using another browser to get to it), run the setup which had the effect of repairing the existing Chrome installation, leaving all settings intact (Home pages, Bookmarks, Extensions)

The reason I put this down to the Restore is that, oddly, I’d been involved with an identical failure of Chrome not starting immediately after a System Restore on another, totally separate PC some 12 hours earlier.

THAT PC is running Winver 20H2 (OS Build 19042.630) The fix was identical to above i.e. running ChromeSetup and effectively repairing Chrome

So apparently, after performing a System Restore on 2, totally isolated machines, Google Chrome got corrupted on both of them!

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

System Restore fails: AppxStaging %ProgramFiles%\WindowsApp 0x80070091

Steps taken.
Part 1/
Install W10. User -Test (No additional updates. No OEM drivers)
Create Restore Point -"Pristine"
Make a system alteration. ie; D/L and Install Google Chrome.
System Restore to RP "Pristine". (Note: Chrome should be gone.)
Successful. Chrome is gone and Edge reset. ??? Chromesetup file removed from \downloads??? Why???
New Restore Point - "Undo Restore" created by system.

Step 2/
D/L and install KB3213986. Reboot.
Make a system alteration. ie; D/L and Install Google Chrome.
Create Restore Point - "Update 1 Chrome"
Make a system alteration. Uninstall Chrome.
System Restore. (Note: Chrome should come back but may not work correctly.)
Fail. 0x80070091

To me that represents a conclusive result.

The next obvious thing to do was to roll back the Update, assuming that this will fix System Restore. However, rolling back the Update DID NOT restore the functionality of System Restore. So now my confident claim, above, is a bit shaky. If performing the update does in fact cause the issue, removing it doesn't put it right.

So now, the next obvious thing is to perform the WindowsApps rename or deletion process, to apply the fix, and run a series of testing to see if System Restore becomes stable.

Results.
Performing the WindowsApps rename fix, instead of deleting it this time, once again resulted in System Restore operating correctly. I have been able to install the remaining updates and flip back and forth between Restore Points without issue.

At this point I am done with it. My testing shows that:

• It is update KB3213986 that causes the problem to occur in the first instance.

• Rolling back the update does not correct the problem.

• Performing the known fix returns System Restore functionality.

• For how long, we don't yet know.

Should you wish to rename the WindowsApps directory rather than delete it, the attrib WindowsApps -h command line can only be performed after the icacls command line.