Windows 10: So did anyone get spring creators update?

I have it installed on real hardware and it is working great.

 

Barman,

I tried to get people to operate in the fashion you suggest since the Insider Program began in October of 2014. A new build would be announced in the News section, and everyone would have to chime in with "ooh! I'm at 47%", or "all updated, working fine". Then would come all the posting about issues, totally unrelated issues all jumbled together, until the thread was literally 100's of comments long and impossible to follow unless you checked in a dozen times a day. Meanwhile, there's a separate Insider Subforum that nobody used. I tried to encourage people to use it instead of the News posting, and got verbal abuse for my efforts. I finally just gave up.

 

Who cares. It is proper to state the day and then month.

 

Why? Let's not and let people post what conflicts with the OS.

 

Yes I have updated 2 computers today via Release Preview Ring. So far everything working great.

 

I`d rather they complain to Microsoft *Smile

But sure, go ahead make a SCU problems and issues thread, I`m all for it.

 

Yeah, someone should make a sticky thread on official release day. *Smile

 

One thread per issue/feature will always be the best way, that way anyone who has an issue, or is looking for assistance, can either start a thread about it, or discuss it with others with the issue and those with troubleshooting experience and find a cure.

If each issue has it's own thread then it will be easy to find for both members and those using Google (or Bing *Wink ),

The major issues and Features can also be the basis for step by step tutorials

 

BTW it's just landed on the Release Preview Ring for me in the UK *Biggrin

Of course I should have expected it to land just as My weekly full data backup had started - postponed, (The backup *Tongue ) it until later or tomorrow (priorities *Wink )

 

You are absolutely correct!

Our suggestion was more of a sarcastic joke. You know that we find a trending phenomena here at TF every spring and fall, when a new official Windows release comes out. *Wink

 

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 *chuckle will keep on trying *Biggrin

 

So...... *Smile 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 *Smile

Any ideas for a blow by blow account of how to get from the raw ESD file to an ISO.

 

Yes, I have replaced the original link with the official, but it seems, it has to be modified to work.

Code: Seite nicht gefunden Anyway, 1803 should be out within 4 days, you can wait for the official version.

 

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