Windows 10: Windows 10 Creators Update rollout: First phase update

I don't get it really. Skylake PC, 980ti gpu, modern SSD, just over a year old and the machine has not got a sniff of the creators update. Not even the privacy settings KB. Whilst our decaying BRIX box running old Pentium, outdated SSD, tortoise like Intel integrated gpu got the update through windows update last night. Seems roll out is pretty random. I'm not going to force it manually but it would be nice to get past this

It took an hour and a half on our creaking box but surprisingly went well with no hiccups. Logged into all the family user accounts on the machine and everything seemed functional with no apparent nasty surprises. Not impressed that MS doesn't respect a users setting for system restore and switches if off by default (why?) and also resets some network share settings. They should leave a users setup alone.

 

This machine was built in Nov. 2016 & purchased mid Jan. 2017. I decided to wait for it via Windows Update thinking it would come fairly early in the process. I'm still waiting my turn. And the longer it goes, the less I'm in a rush to have it get here.

 

My sentiments as well. In my case mine was built in 11/16 but I purchased a week after Thanksgiving.

 

Skylake has caused some issues, Microsoft is working on it.

These are Windows 10 versions that are supported by Microsoft.
1507 will be dropped in May, 2017
Windows 10 release information - current branch, build history

 

I have a Dell 530with a Q6600 and I cannot update it to 1703, I get an error saying the update is not suitable to my machine? Are the older CPU's going to be dumped by MS?

 

With adding the ei.cfg file into the ISO, should we also add a PID.txt as per the Microsoft link
Windows Setup Edition Configuration and Product ID Files (EI.cfg and PID.txt)

 

I have a Dell 530S with an E2200, no problem updating to 1703.

 

I just seen this http://www.techradar.com/news/warning-manually-installing-windows-10-creators-update-could-ruin-your-pc

I have allready installed it on both my pc , have not seen any issues besides the apparent noise of something disconnecting and reconnecting which i cant figure out what it could be, other then that no issues , and my daughter said she has no issues and i installed it on her pc as well. should i worry and roll back or wait for bug fixes to come in updates??.

 

It's just Microsoft saying that if you install the creators update manually you're on your own. Ha.

They just don't want people who don't know what they are doing breaking their PCs and then blaming them.

 

LOL for sure people who can't wait for it to install and reboot the PC in the middle i bet are the ones having issues with it, it takes a while to install and i bet some are very impatient and are like wow it hung nice and they reboot, a friend of mine did it i was like OMG you never do that, then he called me back and said his pc wont boot i was yeah you broke it.

 

No, it's more than that. There are known issues with particular hardware and MS are warning that installing it yourself is a risk if you have that particular hardware. The availability through windows update take that into account, installing it yourself doesn't. It says clearly in post #1 that...

 

The ei.cfg file is not needed. I have done several clean installs with the MCT ISO and my MSDN ISO and if I click "I don't have a product code" on the screen that asks for a key, I get a selection menu where I can pick Home or Pro or Education etc. It does not default to a blind install of Home unless an OEM embedded Home key is detected. You don't need a PID.txt file either, unless you want to auto install a specific version. I have in the past used one to force a Pro install on my laptop that has a Windows 8 Core key. If I don't add the PID.txt with the generic Pro key, 10 Home is installed. The CU however, does not look for Windows 8 embedded keys so now I don't have to bother with a PID.txt file.

 

That's assuming people haven't turned off telemetry and they get accurate feedback from failed updates. *Wink

 

Ms should not even stick this update out there for people to grab VIA the tool if they know from the beginning which you can almost bet someone did, for it to mess up peoples PC, i still say half could be user error.

 

I can't see how a machine would work fine on 1607 and no longer compatible with 1703. I haven't seen or heard of any cases?