The last poster to that thread I linked just posted today and she said she too is having the problem....she mentioned she was on the phone with Microsoft for half an hour with no resolution but they said they were escalating it, so hopefully, they will have a resolution for it...
On a thread I have been participating in regarding the block problem I have been having (seems to be affecting more people than you might think) one person mentioned that one way around the problem for him was to turn off "secure boot" once he did so, the block warning went away...He didn't mention whether he later enabled it again and that it was still ok, only that by turning it off, it provided a quick temporary fix for now...
I was thinking of trying that...would appreciate any input about doing that (turning off secure boot in bios)...ok to do? bad idea? will the computer boot the same with it off? Is there a chance I wouldn't be able to boot up again if I unable it?
Other than that, one of the other guys on there was able to get a direct download of the previous version of windows (Creators Edition from this past Spring) and said doing so solved the problem for him for now...Of course, if I did that and it worked, I guess I would have to stay put on it and not upgrade to fall version...In such a case, would it be best for me to try to skip Fall version and wait for next spring's upgrade instead, or just stay on it until either that I hear that MS has patched or otherwise fixed the problem and I know it would be safe to upgrade again?
Problem solved...thanks to participation on an MS Help forum thread with a group of people there someone found the fix...
Anyone who has the "block bug" simply needs to disable Secure Boot in Bios settings and when you go back, bug is gone....
I restarted an extra time and checked again (just to make sure)...
Then you can re-enable the Secure Boot and bug will still be gone...
Problem Solved!
Enable or Disable Secure Boot on Windows 10 PC Security System Tutorials
Last edited by Brink; 23 Oct 2017 at 14:59. Reason: added tutorial link for more info
Wow great work. I don’t have this issue but followed this with great interest. Thanks for sharing this solution. It really is an appalling bug that MS has overlooked here and I feel for you having wasted so much time wrestling with it
Quote
