1803 problems solved re: sleep, Edge, some HP components failed

Used WinX Update Assistant to update 1709 and download 1803 into friend's new HP Elitebook G5 (great machine).

Problems + Solutions

1. Would not sleep

+ downloaded all driver updates using HP Support Assistant


2. Edge component update or info failures

+ used Edge advanced settings to restrict data input (she uses Firefox, but Windows uses Edge to update unneeded apps), also restricted in main WinX Settings/Privacy (use Google to find detailed how.to)


3. HP installed several programs which failed ("stopped working")

+ we didn't need them, they don't affect the OS (found with Google) and simply uninstalled/deleted them


Even the anticipated Classic Shell issue was a non-issue: after 1803 update, simply clicked to make Classic Shell compatible with 1803

the Classic Shell program is no longer in development since the end of 2017 and its last release does not officially support the 1803 version of Windows 10 & later

Classic Shell • View topic - Classic Shell no longer in development. Source code released

use Open Shell-Menu instead, which is a recent fork of Classic Shell and is most likely to work with recent versions of Windows 10

erpster4 said:

the Classic Shell program is no longer in development since the end of 2017 and its last release does not officially support the 1803 version of Windows 10 & later
Classic Shell • View topic - Classic Shell no longer in development. Source code released
use Open Shell-Menu instead, which is a recent fork of Classic Shell and is most likely to work with recent versions of Windows 10

Well, what you wrote was what I expected.

However that is NOT what happened!!

This past week, on TWO separate HP Elitebooks, a G2 and a G5, both with 1709 installed, after the 1803 download was checked and finished a drop-down box indicated that Classic Shell would be made compatible with 1803 by clicking on the box ....

and it was and still is!

Everything in place and Classic Shell still working the same as it was in 1709 and 1703

Perhaps it was because we used the independent standalone Windows Update Assistant to make the download and installation both times. Dunno, but the truth is posted below >

Note the date of the Classic Shell program, the version number and the date on the computer