- Aug 25, 2001
- 56,587
- 10,225
- 126
Trying to figure out if this is an OS problem, or a problem with the flash drive (apparently not), or my new rig's USB ports (power button was dead, wiring assembly is suspect).
I built a new rig with an FX-8320E in a Rosewill Galaxy-02 case.
I couldn't find my 1709 install USB, so I used a 1703 install USB to put Win10 Home on the rig. Also, I booted in "legacy" mode, it's a Gigabyte LM78T-USB3 R2 board, which doesn't really have the newer UEFI-style BIOSes.
Thankfully, everything including the LAN seemed to be supported by Win10.
I was also using a 480GB Team SSD, and a GT1030 2GB GDDR5 graphics card.
EVGA 400W PSU
Every part was brand new, except for the RAM, which was like new.
So, I figured, after I got it up and running, I would run MS MCT, and make myself a new USB installer with 1709 on it.
I grabbed an Adata 16GB Yellow/Black USB3.0 flash drive, and used that, and I downloaded and ran the MCT on that rig, and twice, in nearly the same place, it gave me "unknown error", and quit on me.
It did give an error code, and when I looked that up, it said something about Windows Update not being able to control starting and stopping the service properly.
Which makes me wonder, I downloaded and ran the newest Shutup10 on that OS too, before I set about using my programs.
Could that have interfered with the MCT? (I run it on all of my Win10 installs, and thus far, hasn't caused a problem with any of them that I know of.)
Or are my USB ports just flaky, and the flash drive was just dropping off and coming up missing, and thus MCT found itself unable to write to the drive?
The drive in question seems to be OK, since I used Rufus to do write-testing to the drive, to 70% or so, before I swapped my Ryzen rig back in place of the new one, and booted it, then I just now used a freshly-downloaded MCT on the Ryzen rig to write to the same flash drive, and made a 32/64-bit 1709 install USB successfully.
I should note that the Rosewill case has one USB3.0 port, and two USB2.0 ports, and the USB3.0 port is disconnected, since that R2 board does't have front USB3.0 (too bad!). I did try using MCT with the flash drive plugged into each USB2.0 slot, and it failed on both of them.
I built a new rig with an FX-8320E in a Rosewill Galaxy-02 case.
I couldn't find my 1709 install USB, so I used a 1703 install USB to put Win10 Home on the rig. Also, I booted in "legacy" mode, it's a Gigabyte LM78T-USB3 R2 board, which doesn't really have the newer UEFI-style BIOSes.
Thankfully, everything including the LAN seemed to be supported by Win10.
I was also using a 480GB Team SSD, and a GT1030 2GB GDDR5 graphics card.
EVGA 400W PSU
Every part was brand new, except for the RAM, which was like new.
So, I figured, after I got it up and running, I would run MS MCT, and make myself a new USB installer with 1709 on it.
I grabbed an Adata 16GB Yellow/Black USB3.0 flash drive, and used that, and I downloaded and ran the MCT on that rig, and twice, in nearly the same place, it gave me "unknown error", and quit on me.
It did give an error code, and when I looked that up, it said something about Windows Update not being able to control starting and stopping the service properly.
Which makes me wonder, I downloaded and ran the newest Shutup10 on that OS too, before I set about using my programs.
Could that have interfered with the MCT? (I run it on all of my Win10 installs, and thus far, hasn't caused a problem with any of them that I know of.)
Or are my USB ports just flaky, and the flash drive was just dropping off and coming up missing, and thus MCT found itself unable to write to the drive?
The drive in question seems to be OK, since I used Rufus to do write-testing to the drive, to 70% or so, before I swapped my Ryzen rig back in place of the new one, and booted it, then I just now used a freshly-downloaded MCT on the Ryzen rig to write to the same flash drive, and made a 32/64-bit 1709 install USB successfully.
I should note that the Rosewill case has one USB3.0 port, and two USB2.0 ports, and the USB3.0 port is disconnected, since that R2 board does't have front USB3.0 (too bad!). I did try using MCT with the flash drive plugged into each USB2.0 slot, and it failed on both of them.
Facebook
Twitter