I've done a clean install as i did it with 2016 LTSB and for that one never mess with partition, neither with fat32 format, LTSB 2016 was installed in other partition aside Windows 7.
are you sure that you was able to boot usb device with this iso on other machines ? To me the iso is the source of the problem, it is probably corrupted. Just use another LTSC 2019 x86 iso and see what happens.
Anyone got a problem with all 1809 versions booting via USB? (inaccessible device) I would stay with my 1607 LTSB but because my new RTX 2080 doesn't support this... Via SATA everything works fine, but I need my OSes portable and I never had a problem with older win versions... The fix with booting into safemode doesn't work. I tried installing new drivers in safe mode, it doesn't work either. Now I'm trying to get the Nvidia driver working in LTSB 2016, but I'm waiting for a backup being copied to a drive... Versions of 1809 I tried to boot via usb: 17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_de-de.iso Windows_10_Enterprise_LTSC_2019_v17763.165_Updated_November_2018-Senftube.iso Win10_1809Oct_German_x64.iso (pro for workstations and normal pro) I tried it to install them to the SSD via rufus or installing it in a VM... Always the same s**tty problem...
Do you mean installing windows from USB installmedia? or booting an installed windows on USB? I now have installed 1809 and updated iso's by FAT32 formatted USB key 100's of times, on different systems/laptops, never encountered any problems. What is the source ISO you've used and did you "modify" it?
Booting a installed win via SATA is no problem at all, everything works fine. Only booting via USB is a hassle I've edited my latest post: Versions of 1809 I tried to boot via usb: 17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_de-de.iso Windows_10_Enterprise_LTSC_2019_v17763.165_Updated_November_2018-Senftube.iso Win10_1809Oct_German_x64.iso (pro for workstations and normal pro) I tried it to install them to the SSD via rufus or installing it in a VM... edit: and taking UEFI or BIOS doesn't make a difference, too edit2: stuff like repair bootloader, mbr, bcd entries, ... i tried everything
Yep but you are not going to like it. Start pulling/disabling hardware audio card (disable in bios pull from slot?), net card etc. Some have left all but the install drive plugged it. Could be getting hung looking for a driver or bucking hardware? Regards
I installed another LTSC version and i still have audio issues. As much as i hate it, i guess i'll go back to Windows 10 Pro until i get some update news.
Did you install the N version or normal LTSC version? I'm asking because I'he had the similar audio issue (on a MSI laptop) when I tried with an old LTSB (i dont remember the version but it was 2016) about a year ago. There was sound, but it was clearly not the same sound I get with windows 7 (the surround was broken, and soundstage was like two dimensional. it felt like i was on a really really cheap sound system). I tried various drivers from realtek and msi but there was simply no change. So I went back to win 7 and decided to wait for a new version of this bloatware-free windows. I've been reading this topic for few days and I can't decide if I should try or not...
That's not the case, as i tried the same ISO on other system and it's booting without problem. Rufus can't manage FAT32 partition with LTSC 2019 ISO.
What's different from the 17763.1 LTSC iso? Nobody complained about that, this new iso just has a old CU integrated.
i see that all these isos are refresh, try with just baseline iso (17763.1) and see what happens. if the problem persists, try to make bootable usb device with the iso using "WinSetupFromUSB-1-8" instead of rufus and see the result.
that's not the point, he obviously was not able to make it work using rufus, so i suggested him to try with another tool as "WinSetupFromUSB-1-8" to see if he will manage to install his win10 edition this way.
I think it shouldn't be a problem with Rufus (I've tried the newest 3.x version and 2.18), or the windows integrated W2Go-Maker. Installing it in a VM directly to the SSD (connected via USB), didn't work either. I think it's a problem of the whole 1809 build. I've tested for fun 1607 LTSB and it worked instantly. Now I've tested a 1709 Enterprise and it works, too, and I can install the RTX 2080 driver there. Only problem is that i prefer the lack of features in the LTSB/LTSC versions. But I'm looking for a 17763.1 LTSC .iso and test it tomorrow.
I think @Thvle may be referring to the file-deletion bug that made headlines last month, and I can understand why one prefers to wait for the 17763.107 refresh over the 17763.1 original.