Chromium & Chrome Will Not Save Passwords After 2004 Update

Thank you Don for your reply. Yes I forgot to mention the issue exists with Firefox also losing sync settings. 

I do use all the 4 browsers I mentioned and OneDrive so uninstalling them is not an option.

I'm also not about to sign in to sync on Firefox, Opera, Opera Beta, Google Chrome, Google Chrome Canary and OneDrive and then sign in to Facebook etc.. in all the browsers after every reboot.

You may be happy to stay on 2004 and sign in to Firefox each time you want to sync. I would not be and am not happy with that so I have gone back to 1909 which is supported till May 2021.

and there's this Don

https://support.google.com/chrome/thread/49967636?hl=en

Opera, Opera Beta and Goggle Chrome Canary are the same.

I also have to sign in to OneDrive and Microsoft Teams after a reboot.

Who knows what MS does anymore.

It looks like MS is not the only player involved in your case ...

... I get 50 GB of cloud storage in Norton 360 if I want it. 

Problems with retaining sensitive data written to disk are often caused by third-party security software, which has to be adapted to every change in the operating system. Providers of this sort of software are not always quick to adapt their offerings in response to major platform updates. Since only some users are affected by the problem you're facing, its cause must lie with the hardware or (most probably) software configuration of the affected machines.

I would start by disabling Norton (or any other third-party security programs) to see if there's any improvement, followed by complete uninstallation if things don't get better.

Hi ¡Firedog,

I'm not sure your statement to Don is accurate. I too have the same issue and I suspect my hardware and software are totally different to Don's. 

I have Avast which was disabled in order to upgrade to 2004 and it made no difference enabling or disabling it to the retention of passwords by the browsers and MS apps. Loads of other users have the same issue so I am pretty convinced it is to do with the upgrade to 2004 and not one of the items on the PC. And everything is running perfectly fine in 1909.

"Since only some users are affected by the problem you're facing, its cause must lie with the hardware or (most probably) software configuration of the affected machines."

a) there are numerous users affected - probably this

https://www.windowslatest.com/2020/08/11/windows-10-may-2020-update-breaks-down-critical-feature/

b) since your first assumption is erroneous and there are numerous users affects it follows your conclusion is probably also erroneous.

The use of "must" is always a no no with all the IT departments I have worked in. Unless you have proven the case then I was always advised in my 40+ years in IT to avoid the use of words like "must"

- must lie with the hardware or (most probably) software configuration of the affected machines.

Also this is patently not true since everything works perfectly with 1909 and it is only on 2004 that there are issues.

My wife's laptop also runs Avast by the way and all her passwords and sync settings are retained after a reboot in 2004. So it is not Avast at fault.

Where did I mention Norton ?

Sorry. I was replying to Don, who did mention Norton.

I have Avast which was disabled in order to upgrade to 2004 and it made no difference enabling or disabling it to the retention of passwords by the browsers and MS apps.  

In order to be able to do their job, security programs have to insinuate themselves into the deepest recesses of the OS. Disabling some or all of its functions may not be enough to prevent interference with the user's legitimate actions. 

Apart from that, some of them install extensions within the browser itself; these would have to be removed as well in order to troubleshoot their potential involvement in the faults you're seeing.

... your first assumption is erroneous 

If you mean "only some users are affected by the problem you're facing," this is clearly true. There have been a handful of cases reported, but I for one haven't experienced the problem, and I've been running v.2004 for several months (currently on build 488).

Also this is patently not true since everything works perfectly with 1909 and it is only on 2004 that there are issues ... So it is not Avast at fault. 

That is, I'm afraid, a non sequitur. 

... I was always advised in my 40+ years in IT to avoid the use of words like "must"

That's a good rule; I should perhaps have written "most probably lies." However, I've seen enough cases in recent weeks to convince me that interference from third-party software is the most frequent cause of otherwise inexplicable problems with this new program. 

Your last statement is revealing, and it shouldn't be too difficult to compare the configuration of the two machines (and the Google accounts involved) to pinpoint why one is affected but not the other. If your wife's machine is not exhibiting the fault after 2004 is installed, doesn't that tell you that its cause lies somewhere else?