Windows 10 2004 build

[ohio_grad_06]

Be careful of this one. I know it's still in testing, but had to work on a system today that had somehow updated to it, and apparently that update removed some files from the user's desktop. I looked and confirmed for example that an Excel file she'd pinned in Excel was not at the location on the desktop that Excel thought it was.

Checked users folder in windows.old, as well as the normal users folder, didn't see any temp profiles or anything. Rebooted a few times, but the file was just gone. Even rolled the update back to the previous build, but her file was still not there. Unfortunately at that point what do you tell them but make sure you save where it will be backed up?

Just letting folks know that this happened, and be on the lookout. Hopefully they will resolve this before this update is released fully.

 

[britechguy]

. . . had to work on a system today that had somehow updated to it . . .

Thanks for the warning. That being said, machines not on one of the insider rings don't "somehow" update to the pre-release versions. That user did something, but what you'll probably never know.

 

[Sky-Knight]

Nuke and pave that machine... because it's the only way to get it out of the beta ring.

 

[ohio_grad_06]

Good thing is the machine in question is 6 or 7 years old. So I'm actually getting quotes for a replacement anyway.

 

[britechguy]

This brings up a question: If you nuke and pave a machine that you've enrolled in the insider/beta ring, does it automatically default back to not be on that?

I've actually never had to do this, and would be curious as to whether the reversion happens automatically or if there is something that needs to be done when doing the completely clean reinstall? I imagine this also might depend on the ISO itself that's used, so if you use the ISO you download from the normal Win10 download page it would likely not allow the insider/beta to install again (as I believe the ISOs are different).

 

[Sky-Knight]

Yes, you have to perform the process to opt into a ring other than default.

Reinstall is how you get out. And the install doesn't magically change unless you change it. It's not a different ISO at all, though I suppose you can get a beta ISO... but usually you "upgrade" into the insider ring just like any other feature update.

Anyway... it's all here: https://insider.windows.com/en-us/getting-started/

 

[SAFCasper]

I'd bet anything the update had nothing to do with the missing file. The user deleted it.

Also, the insider ring doesn't just magically switch itself on. The user enabled it.

Either they are lying to cover their own ass or they are incompetent but click-happy and didn't realise what they were doing. Most likely the first option. Just look at all the steps required to join the insider ring - https://www.windowscentral.com/how-join-windows-insider-program

You don't just "accidentally click" through all those confirmation boxes.


PS.
You don't need to clean install to leave the insider program. You just click "Stop Insider Preview Builds" and select the option "Keep giving me builds until the next Windows release:"

Once the next feature release goes public (ie. out of beta) you are upgraded to it. From here on you are back on the standard update ring.

If you want to leave the insider program instantly though - re-install is your only option.

It's in the guide I linked above for more details.

 

[ohio_grad_06]

At least in this case all should work out. I had rolled them back to the prior Windows 10 build which in their case was like 1703. Tomorrow I am going to manually push their system back to 1909. In the meantime, I've sent quotes for 3 new systems for them to pick from. So hopefully they will select a newer pc and replace it as it's past time to do so.

 

[Sky-Knight]

Lol now we know what happened, the customer was trying to fix it themselves and instead of clicking the update button, they dove through a ton of hoops into the insider build.

 

[britechguy]

Lol now we know what happened, the customer was trying to fix it themselves and instead of clicking the update button, they dove through a ton of hoops into the insider build.

And, reading nothing except the "Yes/Continue/Next" button on each and every screen when doing so. Then blaming Microsoft or saying that, "the computer did it itself!"

 

[Porthos]

"the computer did it itself!"

I get that excuse after a Windows reset.

 

[britechguy]

I get that excuse ["The computer did it itself!"] after a Windows reset.

I cannot think of more than a tiny handful of situations, like, say, destruction by fire or flood, where that `reason` has not been trotted out multiple times over the years.

It gets less and less believable, and wasn't believable to begin with!

 

[BO Terry]

I know this thread is a few months old but I just had a client laptop that tanked drastically in performance after this installed. After install/reboot, it took 6 minutes to Outlook 2019 to load. The only error message was referencing Intel Optane Pinning error and once we rolled it back to the previous version, it was fine. Now, it is trying to install it again and I don't want to until Intel comes up with new drivers. What is the best way to stop this W10 update from installing while allowing other smaller updates to continue?

 

[britechguy]

Intel has almost certainly already produced said updates, and I strongly suggest you use Intel Driver & Support Assistant on that machine.

Intel has been churning out driver updates at a dizzying rate over the last several years. I don't know if they're not supplying same to the OEMs and Microsoft or whether they're just not getting those tweaked and into their libraries in a timely manner. Since they seem to be missing on both computer OEM pages and via Windows Update I suspect Intel.

I have been using Intel Driver & Support Assistant on any machine I touch that I know to have Intel components for this very reason.

By the way, Feature Updates, even under Windows 10 Home, do not apply themselves anymore, and haven't for a couple of releases now. Until and unless the end user activates the "Download and install" link in the Windows Update pane it will remain uninstalled (unless they happen to be using a version of Windows 10 that is out of support or about to be so imminently).

 

[BO Terry]

Intel has almost certainly already produced said updates, and I strongly suggest you use Intel Driver & Support Assistant on that machine.

Intel has been churning out driver updates at a dizzying rate over the last several years. I don't know if they're not supplying same to the OEMs and Microsoft or whether they're just not getting those tweaked and into their libraries in a timely manner. Since they seem to be missing on both computer OEM pages and via Windows Update I suspect Intel.

I have been using Intel Driver & Support Assistant on any machine I touch that I know to have Intel components for this very reason.

I will do that next time I am hands-on or at least, on a Friday afternoon. This client lost critical work time yesterday because of this update and that actually included Dell Pro support working on the issue. We downloaded the newest driver directly from Dell and it didn't fix the issue
but did not use Intel Support Assist. He is in the middle of a big project and very gun shy after yesterday.

 

[britechguy]

Well, they did something to make Version 2004 install.

I have clients who have machines that have been showing the Download and install link for weeks now, and none have spontaneously installed, as that was the whole reason for changing the mechanism to have the end user actually trigger the process.

The above is said presuming they weren't on something like Version 1803 or 1809, and particularly 1803, which is out of support. I just know of very few people who allow themselves to get and stay that far behind the current release.

 

[BO Terry]

They probably did a restart and update without thinking about it. Normally, that's not an issue but it didn't work out well this time. I'm just trying to prevent it from installing temporarily.

 

[britechguy]

What I am telling you is that "Restart and Update" does not now, ever, trigger a Feature Update under typical circumstances. After several years of screaming from a very vocal group of users, Microsoft listened and did change the install mechanism for Feature Updates in all editions of Windows 10.

Of course, for Enterprise and Educational doing Feature Updates is centrally administered. For Pro and Home, unless you happen to be running a really old Version of Windows 10 that is out of support, a Feature Update will not be applied automatically. The end user MUST activate the Download and install link in Settings, Update & Security, Windows Update Pane.

Make sure they know not to do this, for at least a couple of months, and until after Intel Driver & Support Assistant is installed and they've gotten used to applying the driver updates it indicates are needed. One important note is that Intel Driver & Support Assistant is intelligent about the hardware it's running on. I just had someone I know report that one of the updates it suggested on his Dell was for the Dell OEM version of the driver and it pointed him to it. It specifically said not to apply the Intel generic driver in that instance, while the other two drivers it offered were recommended to be installed.

 

[fincoder]

Yes I had a customer yesterday that had just got the 2004 update automatically, they don't even know how to check for updates manually. Not sure what they were on previously.

It broke their Windows Live Mail POP account setup somehow. Renamed store folder, reconfigured account as IMAP, and imported from renamed store folder fixed it.

 

[Metanis]

It broke their Windows Live Mail POP account setup somehow. Renamed store folder, reconfigured account as IMAP, and imported from renamed store folder fixed it.

They must like having to spend money for you to support that Windows Live Mail! I've still got one lady who refuses to give it up even though I warn her every time she hands me a check that she could just use web mail via the browser.