P plinley Contributor Joined Sep 1, 2019 Posts 48 Jan 7, 2020 #21 I thought if you used the "/migratedrivers none" switch on setup.exe, no drivers would be migrated, and I have even tried that... this is the command I have tried: setup.exe" /auto upgrade /compat IgnoreWarning /dynamicupdate disable /showoobe none /migratedrivers none
I thought if you used the "/migratedrivers none" switch on setup.exe, no drivers would be migrated, and I have even tried that... this is the command I have tried: setup.exe" /auto upgrade /compat IgnoreWarning /dynamicupdate disable /showoobe none /migratedrivers none
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 7, 2020 #22 Nope. If there is a device issue, it has to be disconnected and its driver needs to be killed for it to work. Learned this the hard way.
Nope. If there is a device issue, it has to be disconnected and its driver needs to be killed for it to work. Learned this the hard way.
P plinley Contributor Joined Sep 1, 2019 Posts 48 Jan 7, 2020 #23 whoops, I double-posted that one... ok.
P plinley Contributor Joined Sep 1, 2019 Posts 48 Jan 7, 2020 #25 hmmm... I tried to remove all the printers, and even as admin, cannot remove the one assigned by group policy, so I am going to have to remove it from that machine in group policy... I wonder if that is what's causing the issue on all these?
hmmm... I tried to remove all the printers, and even as admin, cannot remove the one assigned by group policy, so I am going to have to remove it from that machine in group policy... I wonder if that is what's causing the issue on all these?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 7, 2020 #26 No way to know at this point, but do go ahead and try.
P plinley Contributor Joined Sep 1, 2019 Posts 48 Jan 9, 2020 #27 I have removed all AMD and NVIDIA drivers, disabled the video device and audio device... still fails during migration.
I have removed all AMD and NVIDIA drivers, disabled the video device and audio device... still fails during migration.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 9, 2020 #28 Thank you. Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Attachments fixlist.txt 29 bytes · Views: 19
Thank you. Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
P plinley Contributor Joined Sep 1, 2019 Posts 48 Jan 10, 2020 #29 I haven't tried that fixlist yet, but after much to do, we have discovered that these machines (at least 1 anyway) will upgrade with a 1607 ISO; however, the update from 1607 to 1809 takes forever. At the same time, we were able to upgrade another to W8.1, then to 1909 in MUCH less time.
I haven't tried that fixlist yet, but after much to do, we have discovered that these machines (at least 1 anyway) will upgrade with a 1607 ISO; however, the update from 1607 to 1809 takes forever. At the same time, we were able to upgrade another to W8.1, then to 1909 in MUCH less time.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 10, 2020 #30 Okay. Keep me posted.
P plinley Contributor Joined Sep 1, 2019 Posts 48 Jan 11, 2020 #31 Holy COW!! That did it!! Now, the question is whether or not all the umpteen thousand other things I did to that machine helped, or if it was just your last fixlist.txt??? What exactly did it do? Is that last one safe for me to run on a few other machines at this site to see if it - alone -works on them as well? THANK YOU!
Holy COW!! That did it!! Now, the question is whether or not all the umpteen thousand other things I did to that machine helped, or if it was just your last fixlist.txt??? What exactly did it do? Is that last one safe for me to run on a few other machines at this site to see if it - alone -works on them as well? THANK YOU!
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 11, 2020 #32 Hi! Yes, I've fixed a dozen machines with this already. This cleared the migration folder.
P plinley Contributor Joined Sep 1, 2019 Posts 48 Jan 11, 2020 #33 So, can we just rename, delete, or move that folder - or the files therein with a script or batch file prior to running setup? And is this a good run line: setup.exe /auto upgrade /compat IgnoreWarning /dynamicupdate disable /showoobe none
So, can we just rename, delete, or move that folder - or the files therein with a script or batch file prior to running setup? And is this a good run line: setup.exe /auto upgrade /compat IgnoreWarning /dynamicupdate disable /showoobe none
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 11, 2020 #34 I do not ever run any parameters on setup.exe, so I can't comment on that, but if the machines are identical in terms of software and thereby the error code you get, by all means, delete the folder with a batch.
I do not ever run any parameters on setup.exe, so I can't comment on that, but if the machines are identical in terms of software and thereby the error code you get, by all means, delete the folder with a batch.