Bork Tuesday, Any Problems Yet?

Manually installed this update today. Too soon to tell but so far so good.

EDIT: What is the Nexus docker @plat1098

 

Trooper: In case you haven't found this yourself already:

search: Winstep Nexus. The website does not use https protocol so I didn't link it.

It's a decorative software that can hook into various Windows processes, specifically Task Manager, in order to facilitate placing them on the docker. Apparently, there was some sort of glitch between that and Windows following KB4577063 where Task Manager would not remember any settings following a machine restart. It would regain full functionality once the docker was de-installed and the machine restarted, so there's a direct cause-effect thing going on here.

I sent a note to the dev. Hopefully, it gets sorted out before 20H2 is formally released.

 

The .NET Preview update installed here automatically for some reason. I thought Preview updates were supposed to be optional.

 

It should have been optional. I ran updates on several PCs today and was not even offered the update. The only thing showing up under optional was drivers.

 

I got bot the .NET and Cumulative updates tonight on my home PC. They were both under "Optional" updates. Win 10 2004 x64 Enterprise here.

 

I'm seeing the Cumulative update but not the .NET. If it is an optional preview at this point I am not greatly concerned but it must not be distributed to everyone at once.

 

I also only saw the Cumulative update but when I selected that the .NET seperately came down too.

 

What I have been seeing of late on these out-of-band Win 10 2004 updates is the .Net update shows in the regular update section. You then have to open the optional update section and then manually select the cumulative update.

 

Same here. Curious.

 

Same here today.

 

Haven't gotten any .NET update myself. Should running an Insider build make any difference? I'm also past the window for general update receipt, it's usually between 12:30 and 2:00 in the afternoon, Eastern time.

Haven't gotten any .NET updates since July 31st.

 

I'm not on the 20H2 version yet but I'm running the Developer Build 20221.1000 on my VM and the .NET is not showing but only the newer Build and installing it now.

 

OK, thank you. Won't hold my breath for any .NETs then.

 

After two bork tuesdays on a Home system announcing "2004 on it's way," last month the 2004 feature update showed up. I couldn't devote the time for it at that point. So today I went in there and it's... gone. Still on 1909, it's reporting up to date.

I'm stumped. Help?

 

You can either wait for the update to eventually be available, or manually update now with the Media Creation Tool. The computer I've typing this on, has always shown that it is up to date and has never said that 2004 is coming. I saw the same on another computer recently too. It came with a clean install of 1909 and I was not offered 2004 and Windows Update, did not say that 2004 is coming.

In theory, there may be some incompatibilities with some hardware in your computer and 2004, which is why it is not being offered. However, based on the experience of installing build 2004 on a number of computers, I can say that more than likely 2004 will run fine. So it should be fine to manually update now if you want.

 

Hi Roger. Does your success include machines with conexant audio drivers as per the known issues for Win 2004 (marked as investigating since 27th May)? That's the reason it is being blocked on my Spectre X2.

 

Thanks for the input. Seems like I'm sharing this experience with good company and I'm no longer stumped. As it stands, I couldn't care less about 2004 or 20H2. My systems can stay on 1909 forever.

I understand that 2004 could be held up contingent on hardware, but it's been five months and with 20H2 due shortly, my stumpability was triggered.

How does that bode for those still on 1909. Straight to 20H2? Or continue waiting for 2004 and then wait for 20H2? Thanks Microsoft! It was easier keeping track of NT4 back in 1990's.

I forgot to mention the i9-9900K/Z390 Win10 Pro system I built in February hasn't even received that "2004 on it's way" yet. It started out with 1909 from an OEI DVD.

And a BTW: In Oct. 2014 I threw up a mothballed E8400/G35 box and started running a Win10 Pro Insider Program Tech Preview on the slow ring. I got off the ring about three years ago. It got the 2004 last month.

As for the vanishing 2004, that's on a Dell i3-6100/H110. I wonder if it was available and then quickly got pulled, perhaps at the behest of Dell.

The Media Creation Tool is a hoop Microsoft shouldn't expect its customers to jump though. They should pay us to use it.

I do remember using MS support to update some one from 17xx to 18xx a while back using Update Assistant. This is one here for 2004:
Get the Windows 10 May 2020 Update
https://support.microsoft.com/en-us/help/4028685/windows-10-get-the-update
There's a link for the Update Assistant; the second bullet point.

Cheers.

 

I don't think any of the computers had Conexant audio. My wife's laptop has Conexnt audio and Windows Update says that the update is coming.

I believe it is due to issues being found with certain hardware after 2004 was released. When Microsoft discovered the issues, they suspended the update for some computers. But, I don't know why on some computers, Windows Update shows that there are no updates and there is no mention of 2004 becoming available in the future.

 

My 4th gen Intel ThinkPad Yoga too. It eventually EOL'd before the Update came!

 

Yeah mine has the same. The banner stating it's coming blah blah blah has been there since MS released version 2004. It's frustrating as HP don't seem to support this laptop anymore, so there will be no driver update from them. The last update HP released for it was MEI firmware and a BIOS update late 2019, so I'm depending on WU delivering a fix. It's a 2016 model laptop but basically looks and performs as brand new .Its a cracking wee machine, so I'll be massively annoyed if all support for it ends in May 2021. I read that some people who have forced 2004 have wound up with no audio what-so-ever, including after rolling back! So don't really want to go down that route....

Thanks for responding.

 

Windows 10 upgrades blocked after installing KB4577062

https://www.bleepingcomputer.com/ne...-upgrades-blocked-after-installing-kb4577062/

 

Thank you for the reminder JRViejo