studio 5000 not working with 24H2

It's described in Rockwell article 1153049 and Rocwkell states correctly this:

The following message may also appear when attempting to upgrade to Windows 11 24H2 on systems with Studio 5000 Logix Designer currently installed. This message will not appear if you attempt a new install of Studio 5000 Logix Designer on Windows 11 24H2.What needs your attentionThe following things need your attention to continue the installation and keep your Windows settings, personal files, and apps.Studio 500 Logix DesignerThis app isn't ready for this version of Windows. You can uninstall this app from Programs and Features now or wait until Windows Update offers this version of Windows once the issue has been resolved.

I have zero idea why you can't freely search for this on Microsoft's website; this is a Microsoft hold for Win 11 24H2 and you would think it should be easy to search a Microsoft webpage and get a complete list, but no.

Anyway, Rockwell reiterates that the fix will be for V34-37 (so again, if you are on 33 you will probably have to upgrade) and:

The anticipated Windows 11 update to address this anomaly is scheduled for end of March 2025, but is subject to change. The message / prompt preventing an upgrade to Windows 11 24H2 on systems with Studio 5000 Logix Designer installed will be removed following the release of the Windows 11 update that addresses this anomaly. This is scheduled for early April 2025, but is subject to change.

So even though the required Windows update should be ready by the end of March, it still requires a Rockwell update scheduled for early April.

Let's say (hope) we're a month away from a fix.

Done the compatibility mode and contacted rockwell support.

They said they have brought this issue up with Microsoft. They said this is something that Microsoft needs to fix.

Studio 5000 Logix Designer error 0xc0000005 on Windows 11 24H2

Bill,

As posted by others, this is an issue with Studio 5000 brought up by W11 24H2. Until a fix is available, there isn't much to do, and Microsoft does not seem to be helping since as a regular user, you can no longer download the ISO for 23H2 to re-install that version.

As per Rockwell, the problem affects all versions 32 onward (up until 37 as of this writing) and potentially even earlier ones; however, if you look at the compatibility list for V32, they list Win 10, and Win 11 is marked as not compatible, unlike 33-37, which specifically list the problem with 24H2.

This may mean that Rockwell decides not to update 32 to fix this problem, so you may have to consider upgrading to V33 at a minimum. Still, you must wait for Rockwell (or Microsoft?) to publish an update before moving to V33+.

Apparently, this is bad enough to be a blocker for Win 11 24H2: I tried to force-install it on an "expendable" PC with Logix Studio 33 through 37, and the update process forced me to uninstall all versions of Studio 5000 or it would not proceed with the installation of 24H2. I'm sure there must be some registry hack to circumvent it, but the point is that Microsoft seems to be officially aware of this and hopefully be working on an update with Rockwell.

There is an update from Rockwell regarding this:

Solution

Updated 09-APR-2025
 
Microsoft has released an updated build of Windows 11 24H2 that addresses the issue.  Information around this Windows build can be found in Microsoft's article KB5053656.
 
Complete the following steps to receive the resolution.
NOTE: Microsoft is scheduled to release a new update on 22-APR-2025.  After installing the 22-APR-2025 update or later, steps 1-4 will not be necessary. 

1. Install the update from Microsoft's article KB5053656.
2. Run winver to display the Windows Version information.  The OS Build should show as 26100.3624 or later.
3. Download the preview from Microsoft https://download.microsoft.com/download/51428a4d-87f5-424e-923a-e9ce487f2e24/Windows 11 24H2 and Windows Server 2025 KB5053656 250309_15101 Feature Preview
4. Follow the additional steps from Microsoft's website, see "Apply a preview to a single device using Group Policy" https://learn.microsoft.com/en-us/troubleshoot/windows-client/group-policy/use-group-policy-enable-update-disabled-by-default#apply-a-preview-to-a-single-device-using-group-policy.

It seems that KB5053656 is required,, not KB5055523.

I am trying on one PC with 24H2; can anybody else try this?

Guys,

I just got a reply from Rockwell:

We are aware that unfortunately, Microsoft's update did not fix the issue- tens of thousands of customers already informed us about it. We have passed this information further to the concerned team and we are awaiting resolution- this time, coming from our side instead of Microsoft's. This technote will be updated as soon as we will have further information.

Although we all want a solution, admitting that the issue is unsolved is a step in the right direction. I hope it won't take much time for a fix.