We took it into our IT department, where our technician Ileana first tried 'sfc /scannow' on the machine and got nothing. Update: Simple fix that workedĪs stated above, we weren't able to do much on our machine due to the lack of admin credentials. It won't work for us until we can convince an IT technician to give us the password to an administrative account. Numitron recommended trying the command 'sfc /scannow' first in those cases. Other users, however, said that didn't work for them. Meanwhile, Reddit user Numitron said they were able to fix the issue by running the Deployment Image Servicing and Management (DISM) tool to manually roll back the January updates using this command:ĭism /Image:C:\ /Cleanup-Image /RevertPendingActions We've learned that Microsoft is aware of the issue and will provide updates for impacted devices as soon as possible. (We finally did spin up a VM to test the BSOD error and couldn't replicate the Automatic Repair issue.) A possible solution It's possible that the BSOD error we were playing with earlier is the true source of our woes, but this new issue makes a lot more sense.
None of the usual quick-repair options have worked, including booting from a Windows installation USB drive or using Safe Mode. We did so, and the machine has been stuck in Automatic Repair mode ever since. Our IT department messaged us that we needed to reboot the laptop again per request of the corporate antivirus software.
