![]() In essence, so your Windows 10 could continue to work. Evidently it is not necessarily a part of a working Windows 10 or it may be even already redundantly covered. For me it started earlier but for others, it happened earlier still. There were a lot of KBs that are in this boat aside from 5004237. ![]() It is my belief that it is not the particular KB that failed to install but something is required to be there on reboot that should have been installed. That I think would give people something to work with. Personally, MS should report what update is missing that is causing the rollback. Unfortunately I had to roll back to Windows 10 because of the CPU and Network bugs, So apparently that missing critical update is also necessary for Window 11? Scary. Once I did a fresh install of Windows 10, I could successfully update to Windows 11. I did give Window 11 a go, but in the install, I was getting the error that my PC could not be determined if it was compatible and rolled back, despite the initial link was offered because my PC was compatible. But having an updateable Windows 10 is a win anyways, even if I have to piece by piece install everything else. :)Ĭurrently I am holding off on Windows 11 until they release a patch (I have an AMD multi-core processor, etc). I applaud your patience as in my books doing a fresh install would have been a tad less painful. It does add credence that there was a critical update but MS failed to inform the user that it was missed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |