Confusion is probably the best (and maybe the most delicate) determination of the situation that has been participating in Windows 10 users for almost two weeks.Since the last Patch Tuesday (March 9), some users experience problems with the spilling of the system into BSOD when trying to print.This was repaired twice, as the first corrections were to cause further problems.Now it looks like Microsoft has suspended these updates.
Defects leading to the stop screen with an error "apc_index_mismmatch for win32kfull.Sys "were only to be the beginning of a series of problems.The first approach to their solution resulted in the fact that BSODs still occurred, and what is more, other print problems appeared, such as shifted content, empty pages or paintings printed entirely in one color.The second series of corrections was to finally fix what the first failed, and also removed the new problems she caused by her.However, it probably failed.
Many reports confirm that the updates of March 18 cannot be installed.First, this was accompanied by the message "We could not install this update, but you can try again (0x80070541)".Now it seems that the update (KB5001649, KB5001648, KB5001638 etc..) has been withdrawn at all and has ceased to be offered by Windows Update.This is confirmed by reports of such editorials as Born City, Windowslatest, Bleeping Computer and Mspoweruser, but...Not Microsoft himself.It's a bit strange that the company has not yet referred to this increasingly frustrating situation.
It is getting harder and harder to understand which of the mentioned updates spoils and which repairs printing.Let us remind you that the main culprit is March Patch Tuesday, and the next - the following update with corrections (and new problems).The best solution would be not tooling them at all (although we will be deprived of the latest security updates at that time).You can also wait until Microsoft releases the second packet of corrections again or immediately goes to the third.The latter option seems likely, because this is the time for the second round of collective updates this month (the latter were updates outside the scope).
