![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
ChrisHarris4!
You are a masochist.
Format C: is for dilettants on my opinion. If a Microsoft technician chooses this extreme solution it means, that they do not know the real cause of the problem.
For teh "format C: "solution you do not need any specialist, only have a good backup.
Ha! I'm not sure it was a format c: as my files were still intact. As it was done remotely I can't be sure. I watched the actions of level 2 and saw them find rollback in the log and the line above was referring to drivers. I am only guessing but he did mention drivers so I suspect that was the root cause.
My message to Microsoft would be rather than test the drivers half way through a big upgrade please do the test first and inform the user that there is an issue before repeatedly resending the upgrade and eventually destroying the code.
How about an optional patch/fix for those stuck on 1709 that surveys a pc for prereqs? After all, they do that before Windows 10 is first installed on a PC.