While some available Win10 ISOs were designed only for 32- or 64-bit usage, there was an ISO that supported both 32- and 64-bit systems.I didn’t conduct a thorough comparison, but the ISOs I downloaded using these sources seemed identical. I could download the appropriate Windows 10 ISO either Microsoft’s Media Creation Tool, the AdGuard website, or a Linux computer.To install WTG, I needed to download a Windows 10 ISO file.To summarize my findings in a single sentence, I concluded that I would get the best results with a reliable 32GB (or larger) USB 3.0 drive (or external SSD) on which I would install the Both ISO (i.e., the Windows 10 ISO that contained both 32- and 64-bit installers) using AOMEI Partition Assistant (though I hoped that eventually I would find a tool that would not default to Win10 Home). The following points capture most of the essential findings in more detail:
To break out of that loop and complete the WTG installation, I had to learn and try a few things. In that case, the error message was “There was a problem running this tool.” That loop mentioned an error code (0x80070005 – 0xA001a) that I also got when running the Media Creation Tool to set up a WTG USB drive. One part of that loop had me looking at a screen presenting the title question: Why did my PC restart? I was setting up Windows To Go (WTG) using Windows 10 and a USB 2.0 drive on an old 32-bit HP Mini 110 1023NR netbook computer. Unfortunately, the setup process was not completing. Instead, I was stuck in a loop. Another post provides what may be a superior solution for some.
I thought I had a solution some of the materials described here were helpful but this project was interrupted, and I am not certain that I do have it.Īt this writing, a few weeks later, my impression was that I might have better results with a SDHC card than with a USB drive, but many computers would not boot from an SDHC card, except maybe if it was plugged into a USB adapter.
0 kommentar(er)
