New
#51
BTW it's just landed on the Release Preview Ring for me in the UK
Of course I should have expected it to land just as My weekly full data backup had started - postponed, (The backup ) it until later or tomorrow (priorities )
BTW it's just landed on the Release Preview Ring for me in the UK
Of course I should have expected it to land just as My weekly full data backup had started - postponed, (The backup ) it until later or tomorrow (priorities )
I've been around on John's forums from Vista in 2008, and in the trade for thirty Years before that, so I know how things work best, and in reality will keep on trying
So...... :) And if this is the wrong place then please move to a new thread.
I'm trying to further my knowledge and have been trying unsuccessfully to create an ISO image from an ESD file. I have a copy of the W10 Spring update (or so I believe) from here (pastebin link in text):
https://www.ghacks.net/2018/04/03/ge...-update-early/
That has given me a raw ESD file of the en-gb version.
I know I have to convert that to an ISO, and I also think I also need to decrypt the ESD file first. Although there is seemingly loads of info available, nothing seems straightforward. Even following instructions doesn't seem to work as the tools mentioned are not straightforward to use and seem to behave differently to how they are described.
I also came across TairikuOkami's post (#37) and wondered how that works. Doesn't it need the ESD file to access in some way ?
I blindly tried the method given and the cmd actions end up with a message as seen below, that a more recent tool is available. If I accept the prompt it just takes me to the Fall update and says thank you very much for installing it :)
Any ideas for a blow by blow account of how to get from the raw ESD file to an ISO.
I just switched to my standard version to the release preview ring last night and installed it that way.
Hi there
just a query here.
Why not run the update as a VM. You don't need to activate Windows as it will work for a little while before giving messages -- should be enough to test to see if things like Networking have been broken (again) etc.
Won't be a full test of course but it should certainly do as a start -- and of course before risking full update on running machines TAKE BACKUP so you can revert if it fails. Wiyh a VM just delete from disk.
I've tried to get people to suggest to Ms that any Windows install should have a 30 day grace period for testing - like W7 and XP did --often one wants to try out and test things -- using the preview / developer editions while a great testing platform aren't quite the same as testing a "bog standard" production type OS.
Cheers
jimbo
Thanks Tairiku, I shall continue having a play.
@ 56 % in case you were wondering. Its getting there......