Windows 10 pro ISO file

Question

Where can we download the preinstalled unactivated Windows 10 ISO image so that we can restore it?

Just installing a ISO image from microsoft dont work without all drivers?

sidxh · Answer

I've had success in doing this. That way if your using sucure boot and such it will still work since it's bit by bit

Good point! I don't like forensic clones because I am an idiot who forgets things - I am liable to lose the clones or overwrite/change partition flags because some other project needed me to. But I can see that as totally being a great solution for disciplined folks.

Eli99k · Answer

sidxh wrote: ↑Wed Dec 30, 2020 8:11 pm Just putting my notes here for those that may be interested.

Usecase : LP Alpha 864s, with activated Win10 - Put a new win10 install on a new M2 SSD with all the original drivers in place.

Problems #1 : I saw all the problems described in this forum thread. The LP alpha images on dropbox are not usable etc - I am not even sure what images they are; I think they are rstrui images, not bootable install images. The microsoft man page to create "bootable USB disk" is also not useful because that method requires an iso image for the bootloader to mount.

Problem #2 : Installed new win10 20h2 on SSD using win10 installation media creator. Easy enough. But then I ran into the unknown and misidentified driver issues. The only recommendation from LP team was to do the intel chipset driver update, which only took care of BT driver. The Intel Gaussian mixture model/1911, serial IO, XR21 USB-UART, ReakTek drivers were not recognized. I needed the SIO/USB UART drivers.

My solution : Luckily, I left my emmc untouched (just disabled it in bios), so I could always boot into the as-shipped drive. I copy/pastad the system32\DriverStore\FileRepository into my SSD. When I booted back into the SSD, I could use devmgmt to update unknown/misidentified drivers using the filerepo location. Funnily, it worked - like it should have if I had been smart about it yesterday. (Usually there's reg hacks to take care of, but this is exactly the same machine and no major reg changes between 20h2 and 1803)

Outcome : Got the superficial results I wanted - No unknown drivers and everything looks like in as-shipped install. Still need to check if the system behavior is at parity.

Opens : Long-term influence of wuaclt on sys behavior; HW stability w installed drivers;

Btw.. if you wanted a copy of your windows on the m.2 ssd or any type of drive.
Step 1. Ubuntu live boot drive. Side note-->May be able to do it in windows as well not sure.
Step 2. DD or bit by bit copy of the 64gb flash to ssd ( I'd use a 64gb flash drive so I can store it on the shelf).
Step 3. Boot ssd
Step 4. Expand ssd.

I've had success in doing this. That way if your using sucure boot and such it will still work since it's bit by bit

sidxh · Answer

Just putting my notes here for those that may be interested.

Usecase : LP Alpha 864s, with activated Win10 - Put a new win10 install on a new M2 SSD with all the original drivers in place.

Problems #1 : I saw all the problems described in this forum thread. The LP alpha images on dropbox are not usable etc - I am not even sure what images they are; I think they are rstrui images, not bootable install images. The microsoft man page to create "bootable USB disk" is also not useful because that method requires an iso image for the bootloader to mount.

Problem #2 : Installed new win10 20h2 on SSD using win10 installation media creator. Easy enough. But then I ran into the unknown and misidentified driver issues. The only recommendation from LP team was to do the intel chipset driver update, which only took care of BT driver. The Intel Gaussian mixture model/1911, serial IO, XR21 USB-UART, ReakTek drivers were not recognized. I needed the SIO/USB UART drivers.

My solution : Luckily, I left my emmc untouched (just disabled it in bios), so I could always boot into the as-shipped drive. I copy/pastad the system32\DriverStore\FileRepository into my SSD. When I booted back into the SSD, I could use devmgmt to update unknown/misidentified drivers using the filerepo location. Funnily, it worked - like it should have if I had been smart about it yesterday. (Usually there's reg hacks to take care of, but this is exactly the same machine and no major reg changes between 20h2 and 1803)

Outcome : Got the superficial results I wanted - No unknown drivers and everything looks like in as-shipped install. Still need to check if the system behavior is at parity.

Opens : Long-term influence of wuaclt on sys behavior; HW stability w installed drivers;

LattePanda · Answer

HI, you can press F7 during booting and manually choose the boot option.
or pls give us your alpha model and SN number, we can help check.

Arcade_Killa · Answer

That did solve my issue but I will mention the reason I was using NTSC formatting was that the Windows Docs you reference mention doing so. So I am now very close to what I need but I want to install Windows onto my SSD and the boot loader seems to indiscriminately choose the 64gb onboard storage for the install. Is there a config file or some setup I should do to ensure it goes onto the SSD?