Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: compatibility issue with windows 11 22H2 new file explorer (Read 2455 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

compatibility issue with windows 11 22H2 new file explorer

I just got 2023-10 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5031354), which was known with new file explorer.
And I noticed that when I open file explorer (any method, such as using win+e, clicking icon in start menu, opening a folder on the desktop, etc) the window of fb2k will flash once. The title and frame is fine, and remaining elements (menu bar, all panels in the platform) will flash.
I think M$ broke something, but other software I use did not have such issue, so I reported here, maybe you can find the problem. Thank you!
fb2k version is 2.0 stable and latest 2.1 preview (2023-10-11), and I use Nvidia RTX 2080 super with latest driver 537.58 (also tried on an old driver, the issue is same.) hope it will be helpful.

Re: compatibility issue with windows 11 22H2 new file explorer

Reply #1
That doesn't sound normal and I don't see that happening. Have you confirmed that the flashing happens with a clean portable install to rule out third party components? Right now I struggle to imagine why Explorer would affect foobar. If it happens with clean portable install too, perhaps Process Monitor log would show something.


Re: compatibility issue with windows 11 22H2 new file explorer

Reply #3
I can reproduce with Default UI. Parts of the UI flicker (such as text and borders).
.

Re: compatibility issue with windows 11 22H2 new file explorer

Reply #4
I just arrived home and I did the test on my another PC (Intel NUC, with integrated GPU Iris Xe, I never install fb2k on this platform.) I tried portable installation and I reproduced the same issue.
Also, I tried a clean installation on the previous PC and saw the same issue again.
Default UI, yes, I use Default UI.

One more useful info: I have a 4K monitor running under 120Hz with my PC through DP1.4, and NUC connected with a 2K monitor with 144Hz, both of them under 8bit (non-FRC).

Re: compatibility issue with windows 11 22H2 new file explorer

Reply #5
On win11 23H2 22635.2419, opening the File Explorer will also cause text to flicker

Re: compatibility issue with windows 11 22H2 new file explorer

Reply #6
Problem noted, thanks for reporting.
Microsoft Windows: We can't script here, this is bat country.

Re: compatibility issue with windows 11 22H2 new file explorer

Reply #7
Some insights / thoughts / ramblings

foobar2000 v1.6.x has this problem as well, so it's not something I changed recently.
I have two Windows 11 machines, both reporting 10.0.22621.2428. One of them has the bug, the other does not.
When Explorer starts, foobar2000 main window receives a registered message (see MSDN RegisterWindowMessage). Exact code, in 0xC000+ range, obviously varies between machines / will probably change with system restart. This message occurs on both machines; on the machine with the bug it is followed by WM_SYNCPAINT, WM_NCPAINT, WM_PAINT and so on.
Unfortunately I'm unable to identify the message because Spy++ is broken on both machines, doesn't log messages. Know any other way of identifying this? oops, VS defaults to launching 32bit spy++ that can't log messages from 64bit processes and isn't telling why.

Edit: the message fb2k gets is "ShellFileOpened"
Microsoft Windows: We can't script here, this is bat country.

Re: compatibility issue with windows 11 22H2 new file explorer

Reply #8
Follow up rant

This hits every most simple window I could make.

The only way to make it go away is WM_ERASEKGND suppression, which Columns UI seems to be good at, better than my code, so it's not obviously affected by this problem, though it's still redrawing stuff, just does a better job hiding it than Default UI.

Pretty much all apps on my system (FileZilla, Notepad++, even Spy++ from MS) are affected by this bug one way or another, with few notable exceptions. Please complain at Microsoft to fix this. Thanks.
Microsoft Windows: We can't script here, this is bat country.

Re: compatibility issue with windows 11 22H2 new file explorer

Reply #9
I submitted a report in the Windows Feedback Hub:

https://aka.ms/AAn2lri

Upvote it if you're affected by the problem and want it fixed.

(Also. this one could also do with some upvotes: https://aka.ms/AAjwm3y)
.

Re: compatibility issue with windows 11 22H2 new file explorer

Reply #10
I'm glad you found out what the problem was, thank you. I just upvoted for the ticket, and I hope they will fix it within this century...