Closed everything411 closed 8 months ago
I'm not sure if 26002 is the minimum affected version because I'm already on 26016. The earliest bug report here is #2030 and it says 26002 is affected.
@Surferdbeere @LammariOm please test this build. https://mega.nz/file/dyUQiLjQ#TJykB0eWuVHVLdfwz7X_dniLDFszVN6TTuXhzI4FBgI
Good investigative work!
From what I understand Microsoft is trying to change the desktop implementation in the recent insider builds.
The changes may end up being different or never reach the final stable build, so checking version may not be a good idea:
Environment.OSVersion.Version.Build >= 26002
What if the first search fails we check for progman child Window as a fallback or something like that?
I don't have insider build with me at the moment, things to verify with this fix:
Looks like things changed again https://github.com/rocksdanister/lively/issues/2074
Looks like things changed again #2074 So what's the solution?
The issue persists on build 26080.ge_release.240308-1400
The
WorkerW
window we created is a child window ofProgman
window on Windows 11 Insider Canary build 26002 and later. This pull request resolves #2030 #2047Spy++ output