Windows 10 Fall Creators Update out 17th Oct

northwalesd

Dandytf wrote: »

Did you follow the 2 usb drive instructuions or use external hdd

Neither, standard Windows Update.

Xbigman

I spent 80 minutes upgrading only to find my 4G data dongle wouldn't work. I had to roll back to the first creators build.
W10 (Fall Creators) detects the device but not what it is. I tried updating the drivers through the Hi Link site but apparently I am up to date. I tried updating the drivers via device manager but its not selectable. If anyone has any idea's please pass them on but for now I'll not go over to the new build.



Darren

techno12

I'm hating W10 at the moment - the pain of updating from 1703 to 1709.

Spent all day (12+ hrs) trying to install it. It always gives a BSOD after the first reboot during the install process (when it's reached 30%). Tried everything, all the 'fixes' on the net, unplugging all drives etc.

The weird thing is I get the exact same problem when trying to update my ancient Samsung netbook. Crash on reboot after 30%.

Which leads me to believe it's a piece of software I have installed on both that's causing it. The only common one is Avast! and I've uninstalled it to no avail.

Bloody frustrating as it looks like a reinstall windows job, but it's odd how I'm getting it on 2 machines, and that there are very few reports of this issue.

Grr...

grumpycrab

^^^ are you upgrading using Windows update or by media? The latter may be worth a shot.

Laz123

Or try the update troubleshoot wizard https://support.microsoft.com/en-us/help/4027322/windows-windows-update-troubleshooter

unforeseen

techno12 wrote: »

I'm hating W10 at the moment - the pain of updating from 1703 to 1709.

Spent all day (12+ hrs) trying to install it. It always gives a BSOD after the first reboot during the install process (when it's reached 30%). Tried everything, all the 'fixes' on the net, unplugging all drives etc.

The weird thing is I get the exact same problem when trying to update my ancient Samsung netbook. Crash on reboot after 30%.

Which leads me to believe it's a piece of software I have installed on both that's causing it. The only common one is Avast! and I've uninstalled it to no avail.

Bloody frustrating as it looks like a reinstall windows job, but it's odd how I'm getting it on 2 machines, and that there are very few reports of this issue.

Grr...

We've just done a version upgrade on around 150 at work. Around 10-12 had this problem, stalling at anywhere between 30 and 45%. All machines are standard build with the same apps on all. Users aren't allowed to install anything.

We ended up rebuilding those machines from scratch. Had to do it by hand because the systems guys hadn't 'got around' to updating the SCCM image.

chunter

These pro-Win10 people, who think there's nothing wrong with the update fiasco, must be Brexit supporters.
Living life in complete denial.

unforeseen

chunter wrote: »

These pro-Win10 people, who think there's nothing wrong with the update fiasco, must be Brexit supporters.
Living life in complete denial.

If you'd tried a bit harder you probably could have tied the Catalonia problem into it as well.

You obviously forget the Windows 7 Service Pack 1 fiasco where loads of people could not install the SP and even clean installs wouldn't allow it.

RumRat

chunter wrote: »

These pro-Win10 people, who think there's nothing wrong with the update fiasco, must be Brexit supporters.
Living life in complete denial.

There is nothing wrong with the update. Millions of updated machines that have had no problem prove the fact.
That said, this is a phenomena that has been happening with all windows releases, anything could affect the process, from the actual download to installed apps to machine configuration etc. etc.
Nope....Not a Brexiteer, but, not seeing the connection, in any way...:huh:

Neil_Jones

The update itself is fine, as above. Its the fact it has to work on millions of different hardware configurations that causes the issues we see when big updates come out and because of this its almost impossible to foresee many problems.

As opposed to MacOS, where, for example, Mountain Lion will run on any Mac that supports Mountain Lion because the hardware inside the machine is all the same, so if you have issues with them you can be sure they're hardware related. Not always so cut-clear with Windows.