Feature update to Windows 10, version 2004 causing issues with credentials

Sorry to hear, but to be honest 'just not surprised' at all. I want to know when MS Windows are actually going to wake up from their convenient, oh it's not our fault and never has been' hibernation and fix this edition. I find it wholly unacceptable and hugely disrespectful of MS on this issue. Each time I contact their help and chat facilities (even allow their remote access) they just go through the same old same routines, and seem incapable of reading previous case filings (they rather put the end user customer through the frustration of having to explain the problem each and every time).

Not only this, when I put a formal typed letter complaint into MS's UK HQ I didn't even get an acknowledgement.

I just want MS to wake up and revisit all that they did on the new Window's 10 edition and retro-fit patches to remedy.

I am burning up hours and hours of non-productive time.

Any badgering of MS by all any any suffering with similar or related problems is what is needed.

Come on MS - just wake up to the issue please.

Thank you!SO far so good, this cmd script idea seems to be working for me. Infuriating issues, this is the 5th PC in two weeks with the same post update problem with windows credentials, particularly impacting Office apps and Adobe products. 

Thanks again!

This has resolved for me, finally with the recognised solution plus a tweak.

Issue:

Windows credentials deleting, particularly after restart, affecting Outlook, Remote desktop, Adobe, LiveDrive etc but Web credentials fine.

Solution:

Right click Start > Windows PowerShell (Admin)

Run this script

Get-ScheduledTask | foreach { If ((xml).GetElementsByTagName("LogonType").'#text' -eq "S4U") { $_.TaskName } }

A list of scheduled tasks may show up, mine reported:

HPCustParticipation HP OfficeJet Pro 6970

If so then open Task Scheduler (Start type in Task Sched etc)

Find the above listed task and right click on it and "Disable"

That's the recognised solution but when I ran the PowerShell script it was still there ... ?

So I also did this:

Right click (on the task) > Properties

In General tab

Select "Run only when user is logged on"

I also went to the triggers and selected the only trigger that was there and unchecked "Enabled" (don't think you need to do this but)

That's it - the next morning credentials were still there - wow!!

A big thanks to all that helped to find this one - was a complete mare.

Don't works.

Microsoft are on the beste way more and more user lost on Apple.

The issue so long time knowed and still no fix. 

Bad Microsoft .... very bad.

This is what finally worked for me: https://www.forbes.com/sites/daveywinder/2020/11/14/microsoft-confirms-serious-windows-10-password-problem-heres-the-5-step-fix/?sh=4aac259d5fcc