However, the Chromium team decided not to attempt to fix the issue because they weren't seeing an uptick in reports from Chrome users in the Windows 10 Insider program. "Formatted the whole PC and installed non-Insider-Build of Windows, restored documents from backup, so far the past three days I haven't had any DPAPI errors and Chrome is working just fine." "I did a 'Reset my PC' where Windows supposedly reinstalls itself (still using Insider Build) with my primary user deleted, DPAPI errors still present and recurring after reinstall," the user reported in late April. The issue appeared to be caused by Microsoft's Windows data-protection application protocol interface (DPAPI). They also "solved" the issue by reinstalling Windows and reformatting the PC. The user who reported the bug was also using Windows Subsystem for Linux 2 and VMware. It also wasn't initially clear whether the problem stemmed from Chrome or Windows 10.
For some reason, users keep getting signed out of Chrome and forced to sign back in.Īs MSPoweruser notes, the behavior was reported to Google's Chromium team during the preview phase for Windows 10 2004, but the team couldn't reproduce the error. The Edge issue has surfaced following Microsoft earlier this month automatically pushing the new browser to Windand up via Windows Update.Ĭhrome users have also reported problems with Google's browser on the Windows Update, or Window 10 2004. The company notes that so far users have only reported some versions of Edge behaving this way, and it doesn't yet have an explanation for why it's launching on startup when it shouldn't. SEE: Windows 10: A cheat sheet (TechRepublic) Microsoft is seeking feedback from users on its forum and has asked tech pros to enable diagnostic data sharing from the browser to get to the bottom of the issue. Microsoft Edge does have a setting, edge://settings/onStartup, to enable the browser to launch as Windows 10 starts up, but users are reporting that Edge is launching regardless of the setting.
0 kommentar(er)
