Replies

Anyhow, technically this dwm.exe issue occurs like this:

Dwm.exe process (in charge of win7 Aero) is slowly acquiring its size after win7 boot starting from some 15,000KB, and after some number of hours when it’s reaching some unclear size around/over 30,000KB it crashes & auto-restarts then.

1 user thanked author for this post.

Elly

D***!

Sorry for misinforming in item 2 above.

Again –  The Desktop Window Manager has encountered a fatal error (0x8898009b).

I’ll prompt further info here.

1 user thanked author for this post.

Elly

INFO UPDATE & FINAL SOLUTION FOUND:

1. Unfortunately after a bit of extensive testing of KB4093113 as installed right over Dec2017 rollup KB4054518 both issues confirmed yet present. Rare, chaotic but present.

It was mainly The Desktop Window Manager has encountered a fatal error (0x8898009b) coupled with an info record The Desktop Window Manager has exited with code (0x8898009b) of dwm.exe v6.1.7600.16385, and even occasional screen crashes, but rarely 2nd issue as leftovers in taskbar of already closed windows . Please refer to a snapshot below where Registry Editor & Notepad windows are actually closed.

Keeping in mind my earlier check with test install of April 10, 2018—KB4093108 (Security-only update) here https://www.askwoody.com/forums/topic/april-2018-patch-tuesday-is-here-and-its-a-biggie/#post-185304 that these issues aren’t related to security basically, I’ve anyhow duly tested all options concerning Meltdown and/or Spectre protection enabling/disabling by setting all available values & their combinations of 2 standard registry keys below:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ DWORD ‘FeatureSettingsOverride’ value = Key not exists (default) or 0 or 1 or 2 or 3

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ DWORD ‘FeatureSettingsOverrideMask’ value = Key not exists (default) or 1 or 3

Then KB4093113 was removed & put to hidden list as usual.

2. Later I found that neither of my win7 machines around – one of a newly built/repaired win7, another one of a few years old install, and the 3rd one of an ancient install – doesn’t include the well-known and widely used for win7 updating after fresh install KB3125574 – Convenience rollup update for Windows 7 SP1 ver. 4 of some April-May 2016 as installed.

https://support.microsoft.com/en-us/help/3125574/convenience-rollup-update-for-windows-7-sp1-and-windows-server-2008-r2

After KB3125574 install and dwm.exe and its linked DLLs version change to 6.1.7601.23403  and successive repeat install of KB4093113 both issues confirmed gone!

END

1 user thanked author for this post.

Elly

It seems KB4099950 of either old revision or a new one is intended/applicable only to installation of  KB4088875 or KB4088878

The indirect confirmation of this idea is a current m$ WSUS approach as below:

If no KB4099950 installed then both KB4088875 & KB4088878 aren’t offered.

If KB4099950 installed then both KB4088875 & KB4088878 immediately listed.

Thus if you don’t plan to install either of these 2 March 2018 rollup and/or preview massive updates then you also don’t need to install this registry patch KB4099950 or can safely remove it if already installed.

2 users thanked author for this post.

Demeter

Yep. Surely. It’s arrived as optional and unchecked.

No problem here. Moreover I guess it’s the first more or less good massive patch released in 2018.

Now it’s already installed by me and seems to be free both from dwm.exe & closed windows leftovers issues as reported by me here earlier for every test install of all previously released massive patches of 2018. My last report of 4 posts total concerning this matter is here:

https://www.askwoody.com/forums/topic/april-2018-patch-tuesday-is-here-and-its-a-biggie/#post-184232

Please hold on – I’ll duly post further testing results here.

Rgds,

 

1 user thanked author for this post.

MrBrian

UPDATE #4 – FINAL & FUNNY:

Meanwhile I’ve installed April 10, 2018—KB4093108 (Security-only update) only for testing purpose aimed to narrow search for a culprit of both issues occurred if any of 2018 massive patches installed and got a funny result – there is no any sign of both issues with any value of win7 registry key of enabling/disabling Spectre and/or Meltdown protection as 0-1-2-3.

Thus these issues aren’t related to security but to some of win7 new features introduced in 2018 massive patches.

END

UPDATE 3:

Sorry, my optimistic guess regarding April full rollup KB4093118 was wrong.

Same 2 issues again. Mainly – The Desktop Window Manager has encountered a fatal error (0x8898009b). Chaotic. A culprit remains unclear but when rollup removed both issues vanished immediately.

Final present win7x64 config:

1. KB4093118 removed & put to hidden list so win7 is now back to a massive patching status of Dec2017 full rollup KB4054518.

2. KB4099950 29kb registry patch remains installed w/o any network issues both before its installation and afterwards.

3. IE11 patch KB4092946 v11.0.9600.18977 build 11.0.56 installed as standalone and performs normally except that odd stuff in its build numbering when previous IE11 patch KB4096040 of late March was v11.0.9600.18954 build 11.0.57!

4. Current list of hidden KBs:

Awaiting for April rollup preview fun. 🙂

END

UPDATE 2:

Assuming the above combination of settings as a bit fragile I’ve finally:

1. Set the 1st registry key to its default value according to InSpectre utility #7:

KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ DWORD ‘FeatureSettingsOverride’ value = 2

2. Replaced a nVidia driver to even older one but released by m$ itself.

END

1 user thanked author for this post.

ch100

UPDATE:

A bit of extra testing report:

Well, while I definitely don’t wanna loose laptop performance with older hardware as Intel T9500 CPUID  10676, and both mentioned issues now mainly occurred/noticed with Meltdown protection disabled [when Spectre protection isn’t yet(?) provided by CPU firmware] thru InSpectre utility by adding 2 win7 default registry keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ DWORD ‘FeatureSettingsOverride’ value = 2

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ DWORD ‘FeatureSettingsOverrideMask’ value = 3

and changing the 1st key value from its default 2 to 3 as below doesn’t return any clear effect:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ DWORD ‘FeatureSettingsOverride’ value = 3

I’ve anyway changed above key value to 3 and then done a clean install of same version (not latest but assumed best) of nVidia driver but this time including its integrated PhysX performance component. And it seems resolved both issues.

Anyhow, I’ll duly prompt here further issues if any.

Meanwhile I assume this April rollup as more or less acceptable for a permanent deployment.

Rgds,

As usual I gave an immediate try install to KB4093118 (Monthly Rollup) for win7.

At the first glance it looks same as all previous massive patches of 2018 – at least so far I see both chaotic dwm.exe errors in log and leftovers in taskbar of already closed windows as reported by me repeatedly like here:

https://www.askwoody.com/2018/patch-lady-new-update-for-windows-7-kb-4100480/#post-179435

Then a bit of odd stuff:

1. It seems m$ gets nuts with IE11 version numbering – now it’s version of the integrated update is again v11.0.56:

https://support.microsoft.com/en-us/help/4092946/cumulative-security-update-for-internet-explorer

which is literally same as it was of KB4089187 included into KB4088875 March rollup.

KB4096040 included into KB4088881 March rollup preview was of v11.0.57

 

2. There is a sense to install KB4099950 – 29KB registry patch concerning this key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI  marked as Recommended before KB4093118, otherwise it’s remaining uninstall in offering list.

I’ll duly prompt further testing results.

Rgds,

4 users thanked author for this post.

woody, Elly, abbodi86, Seff

dgreen:

then pls check for KB4091290 as same massive but out-of-line patch.

when you have both rollup & preview of Feb2018 listed as available for install but same time no rollup or preview of Jan2018 and KB4091290, then either Jan2018 Preview KB4057400 or KB4091290 should be installed.

also you can download Dec2017 rollup KB4054518 from catalogue and try to install it as standalone. if win7 response will be ‘not applicable’ then one of 2018 massive patches is surely installed.

next do win7 system disk cleanup including updates and try update search again.

p.s. also you can try the script to list absolutely all updates installed on win7. it’s tested to perform just fine:

https://www.bleepingcomputer.com/forums/t/597216/script-to-list-all-installed-updates/

yep. it’s said on just revised help page of kb4091290:

https://support.microsoft.com/en-us/help/4091290/windows-7-update-kb4091290

of course this KB4093118  help page content  isn’t accessible at the moment.

maybe a name/number of forthcoming April rollup?

 

1. The last 2 of your pics mean that Jan2018 preview KB4057400 is likely installed

2. MSRT is never a problem in my experience. Pls just install it.

3. Pls refer to z attached pic taken just now. This is how list should look today when you wanna temporarily stop this 2018 mess of patching based on Dec2017 rollup installed status, where:

KB2952664 x 2 = win10 upgrade trash, KB3021917 + KB3068708 + KB3080149 = clear & confirmed snooping.

even more fun.

29kb in offering list vs 203kb in catalogue.

is it a size of .msu standalone installer packing or m$ hidden income for status change from optional to recommended 🙂

Funny.

KB 4099950  – 29kb registry patch-to-patch concerning Meltdown just changed it status from Optional to Recommended, thus it likely seems to be offered to install separately & supposedly prior to any of forthcoming April 10th rollup.

Also both win7 March rollup KB4088875 & preview KB4088881 massive patches vanished from offering list while another March patch-to-patch KB4091290 of 234.9MB remains alive as Recommended.

Rgds,

1 user thanked author for this post.

MrBrian