I don’t find anything posted here regarding Win-11, 24H2 which appears will be foisted on all of us in the near future with apparently no way to stop it. The hardware resource of a longtime client of mine asked me yesterday if I was aware of anything to be concerned about regarding his updating my client’s hardware to 24H2. I thought no but not having 24H2 on a machine I couldn’t say definitively.
My multi-dll veterinary app is 6.3 abc. I have no issues with 23H2.
I am cautiously slow to upgrade Windows major releases until some time has passed with no big issues reported by the Win 11 community. I have been a long time subscriber to www.AskWoody.com and trust Susan Bradley’s advice. I also don’t have the time or inclination to read through all those “kb…” notices. If Ms. Bradley says wait, I wait. Ultimately Microsoft prevails, but their track record “one step forward, two steps back” resonates.
I don’t expect any issues but “never assume”, ask. Thank you for any observations or advice you may offer.
Oops! I meant to have no space between “Ask” and “Woody.com”. However I got a chuckle from the (1). One never knows what interesting stuff there is on the web until you make a mistake. Thanks.
When my win11 upgraded to 24H2 through windows updates, I started getting lots of popup messages because the system couldnt run the systray.vbs script which plays the new animated icons like the animated internet/wifi/network icon, thats part of the 3 icon internet/sound/battery section in the systray.
I suspect some group policy setting had locked down that part of the OS so it couldnt be upgraded, but afterwards I also lost my backups, so who really knows what was going on with this machine of mine.
Anyway a fresh install of 24H2 from the media creation tool reinstalled everything and so far no popup messages telling me windows cant run one of its own vbs scripts.
There are issues with RDP/TsPlus getting disconnected once per minute. The culprit was KB5050094. We had to roll that back in some instances. In others we set both client and server to use TCP only.
Word is that Microsoft has that fixed now. KB5051987 is supposed to be the silver bullet. I’m not in a hurry to find out.
This is not related to Clarion, but lately when I click on a Windows notification, the appropriate window opens, but it is never made active. The opened window stays behind the currently active app windows. I am guessing this is 24H2 related. It is highly unproductive. Happens with Slack, Skype, Outlook, etc.