Share via

KB4535996

Anonymous
2020-03-03T18:50:37+00:00

Newest update KB4535996 is crashing machines. Makes the machines lock up and blue screen at log in screens.  Not able to get into any safe mode and uninstall this update. Forcing rebuild and GPO's to block this particular update. Microsoft says they havent heard of any problems. however when you search the web there is a slue of issues just from this optional update. Anyone else having issues w this KB?

[Thread moved by VM from Windows 7 forum to Windows 10 forum because KB4535996 is for Windows 10, versions 1903 and 1909, not Windows 7]

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

22 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-03-04T18:57:14+00:00

    Seeing this issue with about 200 machines. Uninstalling the update doesnt come off cleanly and still gets lock ups on initial boot.

    29 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-03-05T08:16:36+00:00

    Seeing this issue with about 200 machines. Uninstalling the update doesnt come off cleanly and still gets lock ups on initial boot. 

    I thought it was so. I suggested to my colleagues not to install it at all

    8 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-03-05T08:38:27+00:00

    One short und clear statement from Microsoft please?

    14 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-03-05T09:18:17+00:00

    One short und clear statement from Microsoft please?

    what kind? isn't everything written so far enough? I have no idea what Microsoft wants to do to fix it.

    7 people found this answer helpful.
    0 comments
  5. Anonymous
    2020-03-05T09:27:07+00:00

    Sorry Alessandro!

    I mean, @Microsoft should place a statement.

    7 people found this answer helpful.
    0 comments