Windows 10 Creators Update rollout: First phase update
-
-
-
It's just Microsoft saying that if you install the creators update manually you're on your own. Ha.
"We continue to recommend (unless you're an advanced user who is prepared to work through some issues) that you wait until the Windows 10 Creators Update is automatically offered to you," John Cable, director of program management for Windows servicing and delivery, said on Tuesday.
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.
-
They just don't want people who don't know what they are doing breaking their PCs and then blaming them.
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...
Blocking availability of the update to devices we know will experience issues is a key aspect of our controlled rollout approach. We decide what to block based on user impact, and blocking issues are a high priority for us to address as quickly as possible. During the time it takes to address an issue, we want to limit the number of customers exposed to that issue.
-
-
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.
-
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...
That's assuming people haven't turned off telemetry and they get accurate feedback from failed updates. 
-
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?
-
![]()
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?
You would think that should be the case. I get the impression skylake is holding my machine back from getting it via Windows update as MS has issues with it, seems bizarre to me that all previous builds work fine with this ultra modern cpu yet creators update has bugs with them.
one thing with the constant changing of builds that occurred to me. System specs. As Microsoft keeps moving the goalposts I can foresee a scenario where a piece of software or a game in the future might work only on an older Windows build but no longer work or be supported on a newer build (or vice versa). I'm not seeing system specs to take that into account, a game on steam or retail shelves will list minimum specs as say Windows 8/8.1/10 and this could end up misleading people if they don't specify builds or just totally confuse someone to which ' works on Windows 10 minimum v9999 777.1111.888 change for the sake of change edition' most people means nothing to them.
-
-
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?
Doubt it and haven't seen anything official but others may correct me. Did you get this error when 1703 was rolled out to you thru Windows Update, or did you try manually? Can you post a screenshot of the error?
I have a euro spec'd Dell Dimension 5000 that has absorbed all updates thus far smoother (not faster) than any of the newer machines in my household. Still waiting on 1703 to come through Update and not gonna force it. I'll post when this happens.
Quote
