https://bugs.winehq.org/show_bug.cgi?id=52560
Bug ID: 52560 Summary: w10pro64 and w10pro64v2004 have specific failures: ieframe:webbrowser kernel32:resource msi:msi msi:package shell32:shlfileop urlmon:url wininet:http wininet:urlcache Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com
Eight tests fail only on w10pro64 and w10pro64v2004, or fail there in a way that does not happen on any other VM.
ieframe:webbrowser Invoke_PROPERTYCHANGE failures kernel32:resource systematic timeouts (bug 52559) msi:msi INSTALLSTATE_ABSENT failures msi:package random timeouts shell32:shlfileop ERROR_FILE_NOT_FOUND failures urlmon:url INET_E_DOWNLOAD_FAILURE wininet:http crash (after ERROR_INTERNET_ITEM_NOT_FOUND + ERROR_FILE_NOT_FOUND) wininet:urlcache crash (after ERROR_INTERNET_INTERNAL_ERROR)
In bug 52559 there is suspicion of Windows Defender causing the timeouts.
https://bugs.winehq.org/show_bug.cgi?id=52560
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase
https://bugs.winehq.org/show_bug.cgi?id=52560
--- Comment #1 from François Gouget fgouget@codeweavers.com --- w10pro64v2004 -------------
When starting up the live snapshot a Windows Update process takes a lot of CPU. Maybe Windows is installing an update it had downloaded just before a data cap was added to the network connection and the snapshot was taken.
Also there is a lot of network traffic despite Windows showing that 0 MB of the data cap has been used. Even just the bitrate is suspiciously high (>1Gbps sustained for 10+ seconds). The source of this traffic is not clear. Windows Defender clearly is downloading some virus database updates but there seems to be too much traffic for it to be just that.
w10pro64 --------
When starting up the live snapshot there is a notification that "We can't finish downloading your update". There is also quite a bit of CPU usage from windows update processes. Presumably Windows had started downloading some update when a data cap was added to the network connection and the snapshot was taken.
https://bugs.winehq.org/show_bug.cgi?id=52560
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #2 from François Gouget fgouget@codeweavers.com --- These failures were indeed caused by background Windows Update activity. I recreated these two snapshots on 2022-04-25 after letting Windows calm down and now these failures are gone (well, there's no more failures than on the other platforms).
https://bugs.winehq.org/show_bug.cgi?id=52560
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from François Gouget fgouget@codeweavers.com --- Closing.