Same thing happens on Windows 11 22H2
It causes an explorer crash
EDIT
It seems t occur on any search string of substantial length of 32 or more characters.
EDIT 2
It would appear that when searching longer strings after a crash the search string text is drawn passed the carat. for example
Here is a long strin|g
The carat appears visually before the g but logically it is not i.e typing continues from the correct position despite it looking like it would insert in front of the g.
EDIT3
I was not able to cause the crash using a logical sentence but random garbage did. for example
"This is a very long string of text containing more than 32 characters" did not crash however
"blahblahblahblahblahblahblahblahblahblah" did crash.
EDIT 4
Apparently the carat position bug is a separate issue even a reboot did not fix it. However it only occurs on my main display which is 150% DPI. on my other 2 that are 100% it does not happen. I had a similar issue with an IDE I maintain when using GDI scaling mode. I had to switch to per monitor V2 and handle font sizes myself to correct it. Perhaps I should make a separate post for it?
Stardock Forums
