Windows 10: "You can't install Windows 10 to a USB drive using setup" cure?

**dahermit** · 3 Weeks Ago

My internet searches on that message have yielded two ways of "fixing" that message when trying to install Windows 10 updates using a downloaded Windows.ISO file. The fixes are here:
http://www.tomshardware.com/forum/id...ash-drive.html

My question is: Why are those "fixes" necessary on some computers and not on others? My wife's computer is a twin of mine, and in her registry, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control. "PortableOperatingSystem", is set to "1" and it has downloaded and installed the latest Windows 10 upgrade without having to be set to "0" (presumably telling the update to install on the hard drive rather than a USB drive).

**dahermit** · 2 Weeks Ago

Just to be sure that readers know what the problem is, my Windows 10 Pro will not install the 1709 update to my computer.
From another computer site, I received a way of resetting my computer's update control file. I ran it, but it generated errors.
Here is a screenshot of those errors. I hope someone can provide a way of fixing them.

Click image for larger version.

Name: error2.JPG
Views: 60
Size: 58.1 KB
ID: 182841

**Berton** · 2 Weeks Ago

What I see could be an issue is incorrect commands in the last 2, shouldn't be as many spaces after the > before ren and needs a backslash \ after SoftwareDistribution instead of a space and a backslash \ after catroot2 instead of the space. Such mistypes will always return an error message.

**dahermit** · 2 Weeks Ago

Berton said:

What I see could be an issue is incorrect commands in the last 2, shouldn't be as many spaces after the > before ren and needs a backslash \ after SoftwareDistribution instead of a space and a backslash \ after catroot2 instead of the space. Such mistypes will always return an error message.

It was an, already written, batch file which I ran, so I don't know.
But the "c:\windows\system32> net stop cryptSvc" seemed to work though.
Nevertheless, I cannot find the source of that Regedit batch file now...I have done so many searches on the problem.
In any event, here is a screenshot of the whole batch file as run:

Click image for larger version.

Name: error1.JPG
Views: 37
Size: 97.3 KB
ID: 182915

**simrick** · 2 Weeks Ago

Click image for larger version.

Name: image.png
Views: 38
Size: 19.6 KB
ID: 182914

Could be that you already have a SoftwareDistribution.old and a catroot2.old, so, try renaming them to *.old1 or *.old2.

**dahermit** · 2 Weeks Ago

simrick said:

Could be that you already have a SoftwareDistribution.old and a catroot2.old, so, try renaming them to *.old1 or *.old2.

I am not sure how one would actually do that. I would need a step-by-step before I would even attempt it. Also, note that there were more errors than just two misnamed files.

Here is the link to the downloadable batch file I was talking about (which I ran):
Reset Windows Update in Windows 10

**simrick** · 2 Weeks Ago

dahermit said:

Just to be sure that readers know what the problem is, my Windows 10 Pro will not install the 1709 update to my computer.

So your system currently has 1703 on it?
Can you run winver and post a screenshot?
Have you tried downloading the latest ISO and mounting it, and running setup.exe from within your current W10 OS?

**simrick** · 2 Weeks Ago

Have you run the Windows Update Troubleshooter?

Click image for larger version.

Name: image.png
Views: 2
Size: 26.7 KB
ID: 182916

The batch file you ran is simply a bunch of commands that you could put into an admin command prompt manually. Brink made the batch file, to make it easier to do. But if you're renaming files to filenames that already exist, you'll get an error (like the last 2 errors you got).

If you want to do it manually, the steps are here:
http://www.thewindowsclub.com/manual...ate-components

But I would try the Windows Update Troubleshooter first.

**dahermit** · 2 Weeks Ago

simrick said:

So your system currently has 1703 on it?
Can you run winver and post a screenshot?
Have you tried downloading the latest ISO and mounting it, and running setup.exe from within your current W10 OS?

1703 on my comptuer
version 1703(os build 15063.966).

Been there...done that (downloading the latest ISO and mounting it, and running setup.exe from within your current W10 OS?). It did not work.

**dahermit** · 2 Weeks Ago

But I would try the Windows Update Troubleshooter first.

Troubleshooter did not fix the problem.

Windows 10: "You can't install Windows 10 to a USB drive using setup" cure?

"You can't install Windows 10 to a USB drive using setup" cure?

Where I am as of now.

Posting Permissions