SteveL![]() Veteran ![]() ![]() ![]() ![]() Posts: 262 Joined: 8/19/2005 Location: Boulder, CO ![]() | Jim (aka sneakers007): The advice posted by BBill is a temporary solution to your error. I also have had this error, and backed out Windows maintenance to solve the problem (email conversations with Barry between 4/20 and 4/27). Today, I (re)applied current Windows maintenance to a VM and confirmed that the problem is still there with current Windows maintenance installed. On my VM, I (re)applied KB4549951 and after it was installed, I installed KB4550945 (most recent update). I then recreated the error (different error number than you, but the text of the message was otherwise the same - and easily recreated when running analysis multiple times with "Forced" selected). If you have KB4550945 installed, then KB4549951 no longer shows in your installed list (see snapshot below - taken during uninstall of KB4550945). If you can uninstall KB4550945, then I expect you will see KB4549951 appear as your most recent installed maintenance (at least that's what I see after uninstalling KB4550945). Then hopefully, you can either uninstall KB4549951, or perhaps you have a backup from early April (prior to the KB4549951 update). Hopefully somebody (Microsoft or Nirvana) will fix this. I agree with you, we can't put off Windows maintenance forever. [Edited by SteveL on 5/9/2020 4:02 PM] ![]() |