Hi, like a good number, I started with 8" floppy disks and MS-DOS, and before that paper tape and a 16bit processor in a box with 8k RAM across several cards.... a 2 pass assembler compilation meant literally feeding the tape through twice.
As for a pinpoint solution... occasionally that's possible fairly quickly. Most often, not.
Now, back on the 7th of July, I think I would either have used a System Restore point to revert the update, else uninstalled it to see if that helped.
A key principle is always to try to have a means of reversion and recovery... which is why I've mentioned System Restore and disk imaging... to try to save the sort of pain you're going through now.
As you've not commented on either, I a have to presume you have neither available.
I don't expect you now have a suitable restore point, but you might try uninstalling the update.. probably
UPDATE 6/23: https://www.elevenforum.com/t/kb5095093-windows-11-cumulative-update-preview-build-26100-8737-24h2-and-26200-8737-25h2-june-23.47719/ Microsoft Support: This cumulative update for Windows 11, version 25H2 and 24H2 (KB5094126) includes the latest security fixes and improvements...
www.elevenforum.com
Now that did introduce some particular problems for some... and then came
KB5100998 and KB5121767
Mine is now 26200.8894.
So..given what you say, possible paths of action are:
- uninstall the last update (if that option is available to you)
or
- use an appropriate System Restore point (which you probably don't have now even if SR is enabled).
Logically the possibility that it's the update needs to be excluded.
Another option which would let you revert your build to an earlier state would be an in-place upgrade repair install.
3rd party issues
Assuming it's some 3rd party interference, you would try a clean boot- nothing but time to lose.
However from what you've now said it sounds as if the update might be responsible somehow.
Account corruption check
Create a new user for test purposes. If all is well when logged in as that user, the issue rests with account configuration etc - and generalised repairs are not appropriate.
Therefore:
If you've not yet done that.. new user check.. start there, being the easiest to try.
You can delete the account afterwards.