New
#171
Did you try 17063 without any modification? Including using UUP2ISO to make an .ISO of the install files that Windows Update downloads?
Did you try 17063 without any modification? Including using UUP2ISO to make an .ISO of the install files that Windows Update downloads?
Also, here is another idea from M$, and it might help you directly:
Specifically, the last tweet - removing all peripherals (and, IMO, optionally, all other HDs except the install drive) as well as, after installing 16299, changing the device installation setting to NO before attempting to upgrade to any of the 17xxx builds. Seems another way to accomplish partially what you are trying to do with the driver injection...
Thanks mate, Yes I tried 17063 without any modification then with a mounted iso setup and with USB
I have no SD cards or other USB peripherals connected just the keyboard and mouse
And I never had the second hard disk until after the problem of RS-4s started but I will disconnect the second hard disk and try again
What do they mean by changing the device installation setting to NO before attempting to upgrade how do we do that?
Follow these tutorials:
Enable or Disable Driver Updates in Windows Update in Windows 10 Windows Update Activation Tutorials
Also look at this one: Turn On or Off Device Driver Automatic Installation in Windows 10 Windows Update Activation Tutorials
Interestingly enough, the second one links to the first one :)
Thanks mate done; I’ll download an update without the drivers in the morning and try again
It’ll be worth making an ISO of this one and play about with injecting whichever driver I want into it
After I try and install without drivers first:)
Left the update on and went to bed, thinking I’d wake up to a nice polite screen asking me to “restart now” so I could do the UPP to ISO but the bar-Stuart went ahead and restarted all by itself.
So I woke up to an impolite frozen windows logo with no circling dots instead, now I’ll have to download the update again if I want an ISO. :)
Download finished asking for restart now but I wasted my time downloading the update again because there is only an .esd from yesterdays date
So I could have done the UPP to ISO without downloading again this morning
We live and learn:)
Disabled the second hard disk, pulled the netgear wifi adapter out, pulled the headphones out, pulled the USB keyboard out, clicked “restart now” and pulled the USB mouse out too
The only thing connected was the power supply and monitor through the graphics card
Only to be greeted on reboot by the frozen windows logo with no circling dots:)
One thing - although the UUP2ISO warns that you should make the .ISO before you hit restart, as long as you are not cramped by HD space, you can usually make one after install by looking in the Windows.old folder and then looking in the same path as before (i.e. C:\Windows.old\WINDOWS\SoftwareDistribution\Download\ as an example of the files for 17063).
Next time in case you forget to make it before hitting restart, check that location before you go downloading again, just in case the files are still there.
Of course, as Kari has mentioned, this is not the optimal way to do it, as things may change later on down the road and the files will no longer be there. however, at least for now (and for as long as they have been using UUP), the files are moved into that windows.old folder. Almost all cases that I have seen where they were not have had to do with either low disk space (that folder usually takes up a few GB, so folks with the bare minimum 10 GB free will usually not have that cache there because Windows installer will delete them to preserve as much free space after install) or because they have used DiskCleanup or some other cleaning utility which removes part / all of Windows.old.
I have a 960 GB SSD dedicate to my system drive, so it always has gobs of space and I always have that folder there after a successful install, and the couple of times I have checked, also after a failed install.
Also, did you manage to turn off automatic driver installation in the basic 16299 install yet?