Windows 10 Fall Creators Update

what is this so-called nasty bug?

Only maintain 64-bit machines but intrigued about what this bug is supposed to be?
On some older PC's it tries to execute wrong 32/64 bit code and fails to install. By example I do select 32-bit installation, then error message comes out which indicate it tried to execute 64-bit code. UEEFI boot is fine, problem is with some computers when booting in BIOS mode.
 
On some older PC's it tries to execute wrong 32/64 bit code and fails to install. By example I do select 32-bit installation, then error message comes out which indicate it tried to execute 64-bit code. UEEFI boot is fine, problem is with some computers when booting in BIOS mode.
You must be using a doctored ISO, or perhaps you made your own custom x86 processor in your home fab? I've been doing this since ISOs were invented, and have never, ever had that sort of issue.
 
On some older PC's it tries to execute wrong 32/64 bit code and fails to install. By example I do select 32-bit installation, then error message comes out which indicate it tried to execute 64-bit code. UEEFI boot is fine, problem is with some computers when booting in BIOS mode.

Tks will look out for it. Have not experienced it myself.
 
You must be using a doctored ISO, or perhaps you made your own custom x86 processor in your home fab? I've been doing this since ISOs were invented, and have never, ever had that sort of issue.
Oh, Arthur, MS moles never give up. You should stop now, seriously.

Of course I doctored ISO, it is called Rufus. Otherwise on it wouldn't boot from BIOS. Yes, it would boot UEFI, but not from BIOS. You didn't know this, Arthur? :) :) :)
 
Installed on my 4mbps connection last night. Installed and running ok.

I do get a bit irritated that It has to reindex everything including my mails again
 
Last edited:
On some older PC's it tries to execute wrong 32/64 bit code and fails to install. By example I do select 32-bit installation, then error message comes out which indicate it tried to execute 64-bit code. UEEFI boot is fine, problem is with some computers when booting in BIOS mode.

Mind pointing to the official bug report for this issue since it’s quite serious that I’m sure it’s right at the top of their list to fix
 
Helped someone yesterday. The machine tried to update, and after rebooting, I got this error during bootup: "Windows could not complete the installation. To install Windows on this computer, restart the installation." Hit OK, it reboots, and brings up the error again.

After powering it off a few times, I got the recovery options, and managed to roll it back to the previous version.

Today, it's happened again...
 
After powering it off a few times, I got the recovery options, and managed to roll it back to the previous version.

Today, it's happened again...
Clean install Win7 SP1 ISO. One switch will disable automatic updates.
 
Helped someone yesterday. The machine tried to update, and after rebooting, I got this error during bootup: "Windows could not complete the installation. To install Windows on this computer, restart the installation." Hit OK, it reboots, and brings up the error again.

After powering it off a few times, I got the recovery options, and managed to roll it back to the previous version.

Today, it's happened again...

Unless you spend the time to organise that updates do not happen when you do not want them to, this scenario will repeat itself over and over again.
Put the time aside, DISABLE ALL sw that is running / starting up at start up and let the processes complete.


How do you sign on? With a MS account or a local account?

Of course you can always chicken out and follow the advice to downgrade ......
 
Unless you spend the time to organise that updates do not happen when you do not want them to, this scenario will repeat itself over and over again.
Put the time aside, DISABLE ALL sw that is running / starting up at start up and let the processes complete.


How do you sign on? With a MS account or a local account?

Of course you can always chicken out and follow the advice to downgrade ......

MS account. It's Pro, so I've managed to defer the update 365 days. When I have time, I may do the upgrade manually.
 
MS account. It's Pro, so I've managed to defer the update 365 days. When I have time, I may do the upgrade manually.

One of the first things you should do, is create a local account and use that instead. Then only log in with the MS account IF you want to update Apps and use one drive.

That solves one huge amount of trouble with updates. Good luck with that 365 day deferral!
 
It should be a feature of NTFS file system. Additional NTFS permission for the folders and processes (either inherited from user rights or on the global basis).

Ransomware is relatively new, so as a temporary solution it is welcome (if working), but it requires Defender to be active. Ransomware can wait for the opportunity when you temporary disable Defender and you have to do it at times, no question about. It is a reason Bleeping Computer has requested a separate feature.
 
Last edited:
Seriously... on an IT forum and so many people complaining about unplanned updates.....

Guys, WSUS works even on Windows Home.... use it.

You approve updates on WSUS when you are ready and have tested your software... its that simple. Oh and if you have Windows Home laptops just create a Filename.reg file with the following:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"AcceptTrustedPublisherCerts"=dword:00000001
"ElevateNonAdmins"=dword:00000001
"TargetGroup"="Workstations"
"TargetGroupEnabled"=dword:00000000
"WUServer"="http://your wsus ip"
"WUStatusServer"="http://your wsus ip"

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"AUOptions"=dword:00000004
"AUPowerManagement"=dword:00000001
"AutoInstallMinorUpdates"=dword:00000001
"DetectionFrequency"=dword:0000000a
"DetectionFrequencyEnabled"=dword:00000001
"IncludeRecommendedUpdates"=dword:00000001
"NoAUAsDefaultShutdownOption"=dword:00000001
"NoAUShutdownOption"=dword:00000001
"NoAutoRebootWithLoggedOnUsers"=dword:00000001
"NoAutoUpdate"=dword:00000000
"RebootRelaunchTimeout"=dword:0000000a
"RebootRelaunchTimeoutEnabled"=dword:00000001
"RescheduleWaitTime"=dword:0000000a
"RescheduleWaitTimeEnabled"=dword:00000001
"ScheduledInstallDay"=dword:00000000
"ScheduledInstallTime"=dword:00000003
"UseWUServer"=dword:00000001

To clear just use:
Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]

Note you have to restart for changes to reflect or simply run
net stop wuauserv
net start wuauserv
as administrator. You can Google the settings if you want to set your own but anyway run that and your Windows 10 Home PC will also only update from WSUS server.

Wrote s simple vbs to also check where you currently get your updates from. Can get it here Just save as Filename.VBS

Hell, I have a group of PC's that still on Anniversary because 1st Creators broke an app the people use.
 
Seriously... on an IT forum and so many people complaining about unplanned updates.....

Spot on! :D

It is so silly that every time there is a new launch of windows we get all these complaints about the update process. It is real easy for anyone using WSUS.
 
Spot on! :D

It is so silly that every time there is a new launch of windows we get all these complaints about the update process. It is real easy for anyone using WSUS.

Most people (even here) aren't "it experts", what seems simple to you is not the case for others. Windows update control can be a lot better if ms wanted it to be.
 
Top
Sign up to the MyBroadband newsletter
X