New
#260
my BT folder still present too with 10158
Hi there peeps
Worked perfectly !!!! I'll install the ISO on a VM to test. I have created a bootable USB from the ISO with RUFUS.
Cheers
jimbo
So I now have a laptop running Windows 10158, but still not been able to make an ISO. There isn't a C:\RecoveryImage folder, and no ESD in Sources.
I had a second attempt to capture the ESD, which successfully installed 10158, but when I try to run ESDtoISO, I get the same error as above.
Curiously, when I compare the ESD file from today with the ESD from yesterday (using the old MSDOS fc command with /b to do a binary compare) both ESDs are byte-for-byte identical. So if they are corrupted, I've managed to corrupt them in exactly the same way.. which is good going, even for me. Also, since Windows itself is installed OK, it also suggests the file might be fine.
So I'm wondering if there's something else happening?
Is there another way to check if an ESD is corrupt?
if you are now running 10158 go into the windows-BT folder (hidden) and in the sources folder will be an install.esd..
so far 10158 has not been removing the BT folder after the upgrade..
I don't know - it was created by the installer. However since then I tried to update to 10159 (but it failed) which overwrote that file.
As well as the 10158 files, I now have two 10159 ESDs, (en-gb, 32 bit) downloaded on different machines (one physical, one virtual), which are byte-for-byte identical, but which still don't work with ESD to ISO.