mitchellvii
Well-Known Member
Ok last gasp here. Tried upgrade and failed. Tried ISO and failed. Going to revert back to clean 8.1 and try ISO again. My guess is something may have been farked in my 10074 installation causing the issue.
I gave up for now. I just "Me Too" a bunch on the feedback app.
I find it truly remarkable that MS releases an update that works the worst on its flagship product. How the hell did this POS make it out the door?
If MS doesn't have this resolved within 24 hours someone needs to get fired.
This 10122 issue might be related to the last Firmware Update (and possibly hard-linked files in Windows.old). I know MS is tracking this issue, use the feedback app to "Me Too" if you are seeing the issue.
I'm thinking it was that last Firmware Update which is below the OS layer, so it doesn't matter if you roll back to 8.1....Gabe said a bit ago that they are investigating a potential fix or work around.I have tried this also on a clean 10074 install and on a clean 8.1 install. All failed.