forums.wsusoffline.net

@boco
Any idea, how to fix these bugs (sound, wallpaper, ...)?
I know, that wallpaper stretching is just partially broken (depends on the wallpaper's size), but it's annoying.

boco wrote:The nag screen is EOSNotify.exe, called by two Task Scheduler tasks (in Microsoft - Windows - Setup -- EOSNotify and EOSNotify2). Just delete these tasks and regain peace. Apply the regkeys,too, for good measure.

I will...

boco wrote:Oh, btw. There's something funny: MS partially broke Wallpaper (and some Sound) handling in the final update. For example, Wallpaper stretching might not work at all, background might get black, and sound schemes might change to other ones. Hoo-Ray!

I would be very surprised if M$ didn't use the security patches to screw up their users Win7 installations here by EOL. They will probably screw up minor functions so Win7 will be annoying to use.
Thank you for this info, I will now skip using the latest patches and will stick to my WSUS offline 1180 which is dated 10 aug 2019. I have not experienced any strange behaviour after this update.

I will be interesting to see how long Win7 will be usable. Win XP would probably still be going strong if it wasn't for the browsers. The internet (browsers) are even more efficient than the M$ invented update hell in creating artificial outdating.
The solution may be to run the browsers in a virtual OS, maybe Linux, and then interact with the browser from Win7. Unfortunately I don't have the knowledge (yet) to do this, or even know if it is possible.
Another problem is the antivirus. I have a long time ago switched to MSE, because all other AV's causes more harm than a virus. MSE runs light and is not neurotic or bloated. M$ will probably tell you that they can not take responsibility for an AV to an outdated and insecure operating system as Win7, and will therefore stop updating definitions on MSE, and you should upgrade to the new fantastic Win10 operating system.
What then? I will probably skip installed AV and just run an offline scan once in a while...

boco wrote:Yes, exactly like the Telemetry bullshit was bundled with Security-only patches 07/2019 and 09/2019.

What KB's are that?

aker wrote:@boco
Any idea, how to fix these bugs (sound, wallpaper, ...)?

KB4534314 is the malware. Released on purpose by M$ on 14 jan 2020

Uninstall the KB and the wallpaper works again.

(This is for the wallpaper infection, I don't know about the sound).

I thought about a solution, which does not require uninstallation of an update...

Code: Select all

kb4507456,July 2019 Security-only Update for Windows 7 SP1 and Windows Server 2008 R2 SP1 (TELEMETRY)
kb4516033,September 2019 Security Only Quality Update for Windows 7 SP1 and Windows Server 2008 R2 SP1 (TELEMETRY)

_____

I've read that the bugs are in user32.dll. Only the replacement with an older user32.dll will fix that. Note this was no intentional screw-up, there are Win10 machines hit by this, as well. About a potential fix for Win7, well, guess what.

Currently, the only reliable way I see to solve this issue: Add some code to determine the revision of KB4474419 and subsequent (forceful) installation of this update in revision 3 (or greater) if an older revision has been found on the system. But that's somewhat incompatible with the current behavior of WSUS Offline...

Regards
Dalai

There's only one word adequately describing Windows Update right now: SNAFU.

boco wrote:There's only one word adequately describing Windows Update right now: SNAFU.

Why right now? It has been so for years...

What can you tell about the sound bug?

Before the Rollup disaster hit, WU was somewhat bearable.

______

I cannot tell anything about the sound schemes bug, as I don't experience it, personally. Some users in the MDL forums have their sound scheme constantly shifted to something other (at reboot).

Following is reported as being broken:
- Wallpaper stretching
- Sound schemes
- Screensaver

boco wrote:Before the Rollup disaster hit, WU was somewhat bearable.

Yes, the rollups were invented to take away the tiny amount of control the users had on the update mess.
M$ used every possible dirty trick to force their undocumented quality rollups down in the users throat.
This one was one of their favourites:
M$ make an important security patch and bundle some irrelevant changes in the patch.
The irrelevant stuff must break something in Windows.
Then they put the correction of the irrelevant stuff in the next quality rollup

But this is all over now, with Win10 you have absolutely no control of your own computer anymore...