New
#1470
Still have all my 1809 My Visual Studio (MSDN) ISO's. Not sure why but i haven't dleted them? I will once (if) new ones show up in My Visual Studio downloads.
Still have all my 1809 My Visual Studio (MSDN) ISO's. Not sure why but i haven't dleted them? I will once (if) new ones show up in My Visual Studio downloads.
Okay now I've started seeing files go missing on my tablet but fortunately I didn't delete 1803 so I can roll back.
I just made version 1809 ISO and USB, with all updates making it build 17763.55. Process is quite easy if you want to try, to get media for repair or clean install.
You just need a USB install media for build 17763.1, with install.wim file. MCT install media has install.esd file which can't be updated offline. If you only have ESD based installer (MCT), you must either download WIM based ISO, or convert your MCT install.esd to install.wim.
- Convert ESD to WIM:
- Download WIM based ISO:
- Create USB install media from ISO:
When done, update 17763.1 to 17663.55 as told in this tutorial: PowerShell Scripting - Update Windows 10 USB install media | Windows 10 Tutorials
Notice that downloading updates as told in above mentioned tutorial step 1.1, you should download the last cumulative update KB4464330 , update KB4465477, and all updates published after them (currently just one Adobe Flash Player update).
That's it. Now you have build 17753.55 USB install media for repair or clean installs.
Kari
I am talking about how can Insiders test the fix. I know it has not affected me but would like to be active in testing the fix.
I have decided to install 1803 in a vm, put a few files in documents folder and KFR to another partition/drive l, and then join Slow Ring and wait for the new update of 1809.
I assume the update to 1809 will hit the Soiw Ring, as it is too late for the Fast Ring.
I am also going to try updating 1803 as above in a separate VM using a current 1809 iso.
Then at least I will have tested the new 1809.