Two different clients, neither storing credentials in credential manager. Login required everytime.

Sky-Knight · Oct 15, 2020

That's the fix we could use now on impacted boxes yes, but it won't be indefinate. Heck next month's rollup might fix it... it's hard to say.

But yes, this does seem to be a 2004 bug... interesting that it doesn't impact all installs.

thecomputerguy · Oct 15, 2020

Sky-Knight said:
That's the fix we could use now on impacted boxes yes, but it won't be indefinate. Heck next month's rollup might fix it... it's hard to say.

But yes, this does seem to be a 2004 bug... interesting that it doesn't impact all installs.

TYPICAL MICRO$HAFT

JoelM · Oct 15, 2020

I brought it back forward to 1909 and have used step 4 in this article to defer feature updates for 365 days and quality updates for 30 days. This will be interesting to watch. So far no issues since removing 2004 version.

How to block Windows 10 version 21H2 (and Windows 11) from installing

Windows 10 21H2 is a very minor update, and you may not want to be a beta tester for Windows 11. Here’s how to keep both of the new releases off your system for now.

www.computerworld.com

thecomputerguy · Oct 16, 2020

JoelM said:
I brought it back forward to 1909 and have used step 4 in this article to defer feature updates for 365 days and quality updates for 30 days. This will be interesting to watch. So far no issues since removing 2004 version.

How to block Windows 10 version 21H2 (and Windows 11) from installing

Windows 10 21H2 is a very minor update, and you may not want to be a beta tester for Windows 11. Here’s how to keep both of the new releases off your system for now.

www.computerworld.com

So you ended up using the Local Group Policy editor to keep it on 1909?

thecomputerguy · Oct 16, 2020

One of the stations with the issue is still capable of rolling back ... doing that now.

The main station I've been working on now has a clean 2004 install so I guess I'll need to go back out and bring a 1909 ISO.

thecomputerguy · Oct 16, 2020

Please report back tomorrow if possible, so will I.

thecomputerguy · Oct 16, 2020

First rollback went all the way back to 1903 ... I'll push it up to 1909.

Sky-Knight · Oct 16, 2020

Here's a policy registry file you can use if you've got pro:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"DeferFeatureUpdates"=dword:00000001
"BranchReadinessLevel"=dword:00000020
"DeferFeatureUpdatesPeriodInDays"=dword:00000016D
"PauseFeatureUpdatesStartTime"=""
"ElevateNonAdmins"=dword:00000000
"AcceptTrustedPublisherCerts"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"IncludeRecommendedUpdates"=dword:00000000
"AUPowerManagement"=dword:00000001
"NoAutoRebootWithLoggedOnUsers"=dword:00000000
"NoAUShutdownOption"=dword:00000000
"AutoInstallMinorUpdates"=dword:00000001
"DetectionFrequencyEnabled"=dword:00000001
"DetectionFrequency"=dword:00000016
"RebootRelaunchTimeoutEnabled"=dword:00000001
"RebootRelaunchTimeout"=dword:0000003c
"RescheduleWaitTimeEnabled"=dword:00000001
"RescheduleWaitTime"=dword:0000001e
"UseWUServer"=dword:00000000
"NoAutoUpdate"=dword:00000000
"AUOptions"=dword:00000004
"ScheduledInstallDay"=dword:00000002
"ScheduledInstallTime"=dword:00000002
"ScheduledInstallEveryWeek"=dword:00000001
"AllowMUUpdateService"=dword:00000001
"NoAUAsDefaultShutdownOption"=dword:00000000
"EnableFeaturedSoftware"=dword:00000000
"RebootWarningTimeoutEnabled"=dword:00000000
"AutomaticMaintenanceEnabled"=dword:00000001
"AlwaysAutoRebootAtScheduledTime"=dword:00000000

Each of these lines does stuff, but the one you care mostly about is this one:

"DeferFeatureUpdatesPeriodInDays"=dword:00000016D

16D is 365 days. So 1909 won't update until 11/11/2020. Which only buys you a month... you might have to increase it.

JoelM · Oct 16, 2020

thecomputerguy said:
So you ended up using the Local Group Policy editor to keep it on 1909?

No in step 4 it mentions:
Start > Settings > Update & Security. Click the link marked Advanced options. Under Choose when updates are installed, use the drop-down boxes to defer feature updates for 365 days and quality updates for 15 days.
I set the quality updates for 30 days

JoelM · Oct 16, 2020

thecomputerguy said:
First rollback went all the way back to 1903 ... I'll push it up to 1909.

Interesting. That's exactly what mine went back to 1903. I know it's a risk but I wonder if after going back to 1909 what would happen if I then installed 2004.
Do I take the risk? I'll have to mull that over.

Sky-Knight · Oct 16, 2020

That is a fascinating theory... all of my units were 1909 before going to 2004.

But if an upgrade fault was in play wouldn't that mean the fresh install was immune?

JoelM · Oct 16, 2020

Sky-Knight said:
That is a fascinating theory... all of my units were 1909 before going to 2004.

But if an upgrade fault was in play wouldn't that mean the fresh install was immune?

True. I'm going to watch the machine tonight and tomorrow morning. Then I'm thinking of handing the machine back tomorrow & then if it's ok getting it back in a couple of weeks and pushing it back to 2004 again just to see what happens.

thecomputerguy · Oct 16, 2020

I don't know how many of these computers went from 1903 to 2004 or how many made it to 1909 but I can confirm with certainty that a fresh 2004 install does not fix the issue.

*On some computers

NJW · Oct 16, 2020

Is any of this relevant?

Topic: Win10 version 2004 systemwide password “amnesia” @ AskWoody

See also the various links to other resources in that thread and a potential workaround.

Executive summary: Appears to be caused by an HP printer utility's scheduled task triggering a deep Windows bug. Other stuff that uses the same Windows API may also be implicated.

Sky-Knight · Oct 16, 2020

Code:

Get-ScheduledTask | foreach { If (([xml](Export-ScheduledTask -TaskName $_.TaskName -TaskPath $_.TaskPath)).GetElementsByTagName(“LogonType”).’#text’ -eq “S4U”) { $_.TaskName } }

The above link says running that will highlight an HP service that causes this?

Which implies other things could do it too...

I have an HP printer but do not have results from the above... I also don't have the problem... so there's that.

tek9 · Oct 16, 2020

I have two customers now with this issue. I'm logged into one of them now, and she doesn't have anything HP on her system. Running the Powershell command returns a task created by Carbonite.
I know the other customer has an HP printer as well as Carbonite, but I didn't get a chance to run the command on that system yet.
Not sure I want to disable Carbonite for this, or start to convince her to move to a different product if we don't know for sure this is the issue.

thecomputerguy · Oct 16, 2020

Both systems are the only two systems in this office that have HP Printers installed on them.

Ran the PowerShell command on one which returned:

HPCustParticipation HP ColorLaserjet MFP M278-M281

Ran PowerShell command on the second one which returned:

HPCustParticipation HP ColorLaserjet MFP M278-M281

I looked up the task and it is set to:

Run at 4:30pm on 10/9/2020 - After triggered, repeat everyone 1 hour indefinitely.

Makes sense, sort of, since she is required to login all day long to various services, but it may also go a period of time without having to login, I do not have exact numbers on that period.

They both have the same printer. One has been downgraded to 1903 and I'm bumping it up to 1909. I will leave the other one that is actively experiencing the issue on 2004 and have the user test.

thecomputerguy · Oct 16, 2020

Reporting back ... the user running 2004 who WAS actively experiencing the issue is no longer experiencing the issue and has not for 2 hours. Will continue to monitor.

thecomputerguy · Oct 16, 2020

Third client who is completely different from the first two, just a single laptop, not at all associated with the first company but also experiencing the same issue also had the Task enabled:

HPCustParticipation HP Officejet 4650

Deleted the task and with have him monitor.

JoelM · Oct 16, 2020

I delivered the laptop back this morning with it running 1909. They have a second laptop they are going to get me the first of the week. I'm going to try the Task schedule trick on that one.
Being able to work together on a problem like this is what makes this a great community.

Two different clients, neither storing credentials in credential manager. Login required everytime.

Well-Known Member

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Active Member

Active Member

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

Well-Known Member

Active Member

Similar threads