I did the update of windows to the 1903 version. Report error, the BSOD starts with the indication "UNEXPECTED KERNEL MODE TRAP". Element that caused the problem: intelppm.sys
The system restarts automatically but systematically tries to solve the update problem with the result that shares another BSOD ....I had to do a system restore but I still see the error and update failed.
Do I have to go and look for an older recovery point? And anyway, this damn win 10 will try to reinstall the update sooner or later ...Solutions? Step to win 10 pro and block updates?

Download any patches later as standalone and install in offline with Network disabled.

Click to expand...

You can also use a Microsoft program called Windows Update Show/Hide to block updates until you are ready to install them. It is available on the Microsoft website. A link to the download is contained in this article.

You can also use a Microsoft program called Windows Update Show/Hide to block updates until you are ready to install them. It is available on the Microsoft website. A link to the download is contained in this article.

Microsoft’s propensity to forget its own settings
On three separate occasions in the past couple of years — in November 2017, January 2018, and March 2018 — Microsoft forcibly upgraded Windows 10 Pro machines that have Advanced Options set to defer upgrades. Microsoft has, in effect, ignored its own settings. You can think of these incidents as accidents, or the result of overworked or overly zealous individuals. I, for one, am not so magnanimous.

These aren’t fly-by-night reports, or wails of pain from users who forgot to turn something on or off. All three have been documented by Microsoft as being Microsoft mistakes, in nooks and crannies of its various posts.

Oddly, it seems that the metered connection trick kept working in the face of all of those “oopsies.” You may well want to set your internet connection to metered, even if you use Windows 10 Pro, Enterprise or Education. Belt and suspenders and all that.

Microsoft’s official back door: The last, and most nefarious of the three “oops” events involves a, uh, feature called Update Assistant and its executioner program, updateassistant.exe. The poorly documented Update Assistant has been around for a long time, but its intrusive nature came to light when it started (erroneously, according to Microsoft) ignoring the Windows Update settings that were supposed to block installation of the next version of Windows 10.

Update Assistant has evolved. You may have seen KB 4023057, the “Update to Windows 10 Versions 1507, 1511, 1607, 1703, 1709 and 1803 for update reliability,” which has been released and re-re-re-released dozens of times (see Rick Corbett’s description). This “Remediation Shell” (formerly “WaaSMedic”) patch is intended to (in the words of abbodi86):

Fix and reset Windows Update-related parts to their “supported” configuration, i.e. restore registry settings, services status, schedule tasks, clear disk space, and launch UpdateAssistant.exe if installed. Mainly it’s meant to pave the way to receive the latest updates, whether quality updates, or feature update to latest Windows 10 version… it evolved from just fixing the Registry to restoring tasks and fixing the drivers DB, and compatibility for UAC management.. the main purpose or function did not change: re-allow blocked or disabled Windows Update.
Microsoft’s so gung-ho on blasting away your Windows Update blocks that it’s set up a regimen worthy of the finest malware. Of course, from Microsoft’s point of view they’re simply correcting any bugs that may have been introduced in the upgrade process. Defeating those who actively block the upgrade is just a bit of fortuitous collateral damage.