Chromium & Chrome Will Not Save Passwords After 2004 Update

It's a good job you replied when you did: I was half-way through composing a reply suggesting it was time to re-install Windows*, since PowerShell, Task Scheduler and DISM all seemed to be broken. I'm glad that now doesn't seem to be necessary.

Please open Task Scheduler again. I see from your earlier screenshot (sorry for not noticing before) that you hadn't opened the Task Scheduler Library before looking for S4U tasks. Dismiss the error message about FeedSync if you see it again, and maximize the window before clicking on Task Scheduler Library in the left-hand pane. Then go hunting for tasks with Do not store password enabled. 

* One reason for my hesitating to suggest this was that there was a bug in a November update (19042.630?) that meant it wasn't possible to do an in-place upgrade and keep personal files. This was soon corrected, and I see you're already up to 19042.685, so that's no longer a problem.

Please ignore my December 7th post.

I have tried again and got the DISM tool to work.

Screenshot below but the result states there are no integrity violations which is not what you thought was the case.

This morning I have installed the latest update to 2004 20H2 and first impressions are that the problem of not saving passwords and cookies remains.

So there still seems to be a bug  in the original 2004 composition.

I am struggling to get DISM to work and assume therefore it is broken.

On that assumption I am trying to follow the alternative route but as I have not done this before I am unclear how to input my source.

However, if your Windows Update client is already broken, use a running Windows installation as the repair source, or use a Windows side-by-side folder from a network share or from a removable media, such as the Windows DVD, as the source of the files. To do this, run the following command instead:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Note: Replace the C:\RepairSource\Windows placeholder with the location of your repair source. For more information about using the DISM tool to repair Windows, reference Repair a Windows Image.   

I have a Win 7 system copy and backup from about two weeks ago on an external hard drive (D). All my File History backups are also on this external drive.

Could you suggest the appropriate command please?

Hi Barry, 

This has been escalated internally and a Windows fix is on the way, my reply for the system-wide password issues is intended as a workaround to use until the fix is available. You're in great hands with ¡Firedog to ensure that your Windows installation is repaired prior to the update. 

I want to thank you (and everyone else sounding off in this thread) for your posts around this issue, I'm reviewing threads here on the Answers community and passing the feedback and concerns on to the product teams. 

-Alex

OK, thank you. You have now demonstrated that some bits of your Windows installation just aren't working properly, even though the operating system itself seems to be functioning. While your computer is in this state, it's impossible to say whether the upcoming Windows Update that is intended to fix the original 'missing passwords' problem will also work for you, so it's worthwhile trying to fix your computer to avoid other problems in the future.

Windows provides some basic tools do repair the installation, which includes not just the operating system itself but also hundreds of ancillary utilities and libraries (like Task Scheduler and PowerShell). I suggest that you take the time (possibly a few hours) to try the first two of these, but first, I'd ask you to uninstall Malwarebytes completely. Use the MB support tool to do this; when you get to step 11, say No! Restart the computer after doing this. 

Then follow the steps in this article: Use the System File Checker tool to repair missing or corrupted system files (microsoft.com). DISM will try to replace any faulty bits of the installation with new ones; when it's finished successfully, the System File Checker will examine the operating system to confirm that all is now well. Both tools will report back with their results; let's hope there weren't any problems with them that need further work. Be sure to make a record of any messages you see. It's a good idea to restart the computer after DISM has finished before going on to use SFC.