KB4032188 issue...

Vaio 7 said:

Just installed KB 4032188 on 3 laptops x64 and each time I install it, 3 times actually, because I revert back from an image backup, it gives me the exact error: on 3 systems.

Description
Faulting application name: svchost.exe_AppReadiness, version: 10.0.15063.0, time stamp: 0x02799ef5
Faulting module name: ntdll.dll, version: 10.0.15063.447, time stamp: 0xa329d3a8
Exception code: 0xc0000374
Fault offset: 0x00000000000f775f
Faulting process id: 0x1388
Faulting application start time: 0x01d30cb11873e98c
Faulting application path: c:\windows\system32\svchost.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 1d840448-215b-4d42-b250-03e706c862a6
Faulting package full name:
Faulting package-relative application ID:


Sfc scan and Dism online commands are both clean.
The error is produced during the second phase of the updating process, between 30 and 100%, but the update shows as successfully installed.
Any help appreciated.

Regards,

Maybe you should try to disable "App Readiness" altogether in services and try the update again. I remember over a year ago, my computer was taking more than 6 mn to boot. That was so nerve racking that I took the time to run the clean boot procedure and happened to nail down the culprit. It was the App Readiness. After completely disable the latter, the problem was resolved and my PC took only 1 mn or so to boot.
The change was so drastic that I was amazed, because it took me more than one week to figure this one out. see also screenshot below:

Hi,

Just a quick note, in order to clarify things, each time I install that update, it is always showing as successfully installed, the problem is that it installs and it produces that error. I already tried your suggestion long before you post it, and guess what, that particular update needs to "touch" something in App Readiness service, if it's disabled then the update refuses to install and initiates the procedure of "reverting changes...".
In all cases, exception code 0xc00000374 indicates heap corruption and it's up to Microsoft to fix it. I will try today the latest Cumulative Update, when released, and report back. If it installs ok, then I'll skip KB 4032188.
Thanks.

@ Vaio 7,

I didn't know that you have tried to disable App Readiness and got no positive results. When I had problems with it, I completely disabled it and never put it back on "Manual" which is the default in Services. The subsequent CUs from Microsoft did, not me. As you can see from my screenshot, it is on "Manual" now. I am really looking forward to seeing how it turns out after you try the latest CU, when released, as you mentioned.

IronZorg89 said:

@ Vaio 7,

I didn't know that you have tried to disable App Readiness and got no positive results. When I had problems with it, I completely disabled it and never put it back on "Manual" which is the default in Services. The subsequent CUs from Microsoft did, not me. As you can see from my screenshot, it is on "Manual" now. I am really looking forward to seeing how it turns out after you try the latest CU, when released, as you mentioned.

I tried also the latest Cumulative Update KB 4034674, same critical event is logged. After one more reboot it does not show up anymore so it's a Microsoft thing. No other errors or warnings in Event Viewer.
Found also a similar post: https://answers.microsoft.com/en-us/...d-678bffe9b63f

Vaio 7 said:

I tried also the latest Cumulative Update KB 4034674, same critical event is logged. After one more reboot it does not show up anymore so it's a Microsoft thing. No other errors or warnings in Event Viewer.
Found also a similar post: https://answers.microsoft.com/en-us/...d-678bffe9b63f

I am really glad to hear that you don't have "No other errors or warnings in Event Viewer". One thing for sure, Microsoft had problems with this service "App Readiness" not long ago. As I said in my explanations above, it was causing my PC to take over 6 minutes to boot; and I decided to disable it completely. I never put it back to "Manual" myself. Microsoft did. That means they had fixed the issue because my PC has been booting normally.

BTW, thanks for the link explaining the same problem. Another proof that there was some sort of an issue with that service (App Readiness)..:)