Is version 1703 stable enough for clean installation?

So I done a manual upgrade to the Creators Update a few days ago but appear to have a corrupted user profile/s and possibly even a corrupted upgrade installation.

I'm not sure what to do, I could transfer user files to a new user profile but it may be more trouble than it's worth and I suspect the Windows installation may be corrupted also so could be pointless.

I could clean install version 1703, but is it deemed stable enough? I could also roll the update back or restore the 1603 system image I took before hand. Recommendations? These issues really give me a headache!

If you are backed up consider a clean install. I had upgrade problems that were related to inadequate free space in the FAT32 partition. After this was fixed there were corruption problems. These were improved with chkdsk /f /r and sfc /scannow. A clean install was performed and so far everything is back to normal. There are naturally bugs with upgrades and these require windows updates over time for fixes. Currently dism restore health has a bug and is not working for 1703 but is working for 1607. If you choose 1607 it is unclear when you will receive an unexpected upgrade to 1703. Many people have asked how to prevent upgrades. I came across one link that indicates you can allow downloads and then not allow installation. So you have blocked the upgrade. Currently I am using 1703 in two computers, one had a clean install and then had a problem with net framework that was fixed and the other was upgraded from 1607 to 1703 and has had no problems.

zbook said:

If you are backed up consider a clean install.

So right now I'm thinking it might not be a user corruption issue as some of these issues seem to persist over new user profiles as well. Perhaps it was an issue with the upgrade process over my particular configuration. As it doesn't seem to be profile related I guess my options are to roll back and defer updates or clean install 1703. Even if you defer the updates 1703 is going to be inevitable anyway, so maybe clean installing 1703 and baring the issues (if they're still even present with a clean install) might be the better option, then I'm sure what ever issues remain will be fixed with updates. ..

We seem to have conflicts about sticking with 1607 for now or baring with 1703 issues. The way I see it is 1703 will be inevitable anyway, and if issues were that bad Microsoft wouldn't be releasing the update...

I'm a little concerned for the less tech savy out there who may have issues with the upgrade already or are still awaiting it. Surely if issues were this bad Microsoft wouldn't be releasing the upgrade? It would be frustrating for the less tech savy to have to find they need to clean install the latest version after the upgrade behaves strangely...

No issues at all with the Creator's Update on the dozen computers on my home network.

Kol12 said:

We seem to have conflicts about sticking with 1607 for now or baring with 1703 issues. The way I see it is 1703 will be inevitable anyway, and if issues were that bad Microsoft wouldn't be releasing the update...

What conflicts? I don't see anyone saying to stay on 1607. I'm not saying there aren't people, but it certainly doesn't seem to be a large number of them.

Kol12 said:

I'm a little concerned for the less tech savy out there who may have issues with the upgrade already or are still awaiting it. Surely if issues were this bad Microsoft wouldn't be releasing the upgrade? It would be frustrating for the less tech savy to have to find they need to clean install the latest version after the upgrade behaves strangely...

Don't make the mistake of thinking that your issues are being experienced by everyone else, or even a large majority. The vast majority of people simply don't have any issues with upgrades, but there will always be some percentage who have systems that cause issues. I find that many times this is because the user has tried to customize their system in a way that the upgrade wasn't tested with.

Mystere said:

What conflicts? I don't see anyone saying to stay on 1607. I'm not saying there aren't people, but it certainly doesn't seem to be a large number of them.



Don't make the mistake of thinking that your issues are being experienced by everyone else, or even a large majority. The vast majority of people simply don't have any issues with upgrades, but there will always be some percentage who have systems that cause issues. I find that many times this is because the user has tried to customize their system in a way that the upgrade wasn't tested with.

Yeah - you rarely see problem posts from somebody running a bog standard laptop. More often self built PCs with fancy nvidea graphics, and people have done regedits etc.

Recently, a person complained that there was a bug in Windows 10 because it would not read both partitions on a 3TB mbr drive (2+1) but claimed Windows 7 did!

Of course, it was possible to read over 2.2TB on an MBR derive in Windows 7 but you had to install special drivers to cheat OS (basically 2 mbrs). Guy was adamant Windows 10 should have handled these drivers failing to understand the world has moved on with UEFI and GPT being the norm now.

NavyLCDR said:

No issues at all with the Creator's Update on the dozen computers on my home network.

Upgrades or clean installs?

I tend to customize Windows a lot so possibly that's where the issues lie.

The missing icons seem to be common in the CU and probably the most noticeable one, but I think I'm going to clean install which may be easier and more likely to set things straight...