Sage 100

@Robert Osborn I posted earlier today about a customer that had two computers that would not open a couple of the Inventory Explorer menu items.  The user would click on the menu item and nothing would happen.  Today, I uninstalled and re-installed workstation setup and the menu items worked again.   Have you tried uninstalling using Control Panel programs and features then re-installing?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

This was reported about a month ago

Sage 2022 and Windows 11 25H2 - Sage Freezing, Locking All Users | Sage 100

25H2 is a commonality

@Greg Stiles , how did your issues resolve out?

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!
------------------------------


Original Message:
Sent: 02-24-2026 17:18
From: Doug Higgs
Subject: Sage does not open tasks

@Robert Osborn I posted earlier today about a customer that had two computers that would not open a couple of the Inventory Explorer menu items.  The user would click on the menu item and nothing would happen.  Today, I uninstalled and re-installed workstation setup and the menu items worked again.   Have you tried uninstalling using Control Panel programs and features then re-installing?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

@Robert Osborn I posted earlier today about a customer that had two computers that would not open a couple of the Inventory Explorer menu items.  The user would click on the menu item and nothing would happen.  Today, I uninstalled and re-installed workstation setup and the menu items worked again.   Have you tried uninstalling using Control Panel programs and features then re-installing?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

HI @Doug Higgs, Yes I uninstalled from the control panel (more than once) including uninstalling all C++ and crystal runtimes,then rebooted and reinstalled.   All under an administrator account.  
@Jeff Schwenk Greg's issue is not quite the same as mine.  His at least starts to open the task.   Mine does nothing. It does not affect any other users. 

@Robert Osborn I posted earlier today about a customer that had two computers that would not open a couple of the Inventory Explorer menu items.  The user would click on the menu item and nothing would happen.  Today, I uninstalled and re-installed workstation setup and the menu items worked again.   Have you tried uninstalling using Control Panel programs and features then re-installing?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

Sooo...  The IT guy SAID that he had uninstalled the security software and tested.  I just got this from him, bearing in mind that when after Scott's review we suggested uninstalling the security software he said "everyone wants to blame the security software.."

I believe I found the cause of the issue but I am unable to explain why it's happening. As you know, the process that runs when starting Sage 100 is called PVXWIN32.exe. When each module is opened or other windows within Sage open, another instance of PVXWIN32.exe is opened. I found that the zero trust software (ThreatLocker) would allow the initial PVXWIN32.exe process to run and spay the window, but then it was preventing the additional windows from displaying the screen, and here is where it gets strange. ThreatLocker's primary function is to stop apps that have not been pre-approved from running. In this case, it's letting PVXWIN32.exe run and that's how we are getting Sage 100 started and logged into. Then, it's allowing the PVXWIN32.exe process that is started with opening a module but just not allowing it to display the window, something ThreatLocker has never done before. First issue is PVXWIN32.exe is already allowed and is already running. Second issue, ThreatLocker is actually allowing the second or third instance of PVXWIN32.exe to run in the background, but won't let the display of the window to occur, this is something we have never seen and technically it should be happening to everyone at CLC as they are all running ThreatLocker and using the same set of app policies as the policies are managed per customer and applied to all machines at that location. I'm going to have to open a ticket with the ThreatLocker support team tomorrow to get to the bottom of this issue. I'll update you in the morning.

Sooo...  The IT guy SAID that he had uninstalled the security software and tested.  I just got this from him, bearing in mind that when after Scott's review we suggested uninstalling the security software he said "everyone wants to blame the security software.."

I believe I found the cause of the issue but I am unable to explain why it's happening. As you know, the process that runs when starting Sage 100 is called PVXWIN32.exe. When each module is opened or other windows within Sage open, another instance of PVXWIN32.exe is opened. I found that the zero trust software (ThreatLocker) would allow the initial PVXWIN32.exe process to run and spay the window, but then it was preventing the additional windows from displaying the screen, and here is where it gets strange. ThreatLocker's primary function is to stop apps that have not been pre-approved from running. In this case, it's letting PVXWIN32.exe run and that's how we are getting Sage 100 started and logged into. Then, it's allowing the PVXWIN32.exe process that is started with opening a module but just not allowing it to display the window, something ThreatLocker has never done before. First issue is PVXWIN32.exe is already allowed and is already running. Second issue, ThreatLocker is actually allowing the second or third instance of PVXWIN32.exe to run in the background, but won't let the display of the window to occur, this is something we have never seen and technically it should be happening to everyone at CLC as they are all running ThreatLocker and using the same set of app policies as the policies are managed per customer and applied to all machines at that location. I'm going to have to open a ticket with the ThreatLocker support team tomorrow to get to the bottom of this issue. I'll update you in the morning.

Bob - You gave a great opening description of this. Run it through Gemini Pro.

Here are some of the AI generated suggestions:

Sooo...  The IT guy SAID that he had uninstalled the security software and tested.  I just got this from him, bearing in mind that when after Scott's review we suggested uninstalling the security software he said "everyone wants to blame the security software.."

I believe I found the cause of the issue but I am unable to explain why it's happening. As you know, the process that runs when starting Sage 100 is called PVXWIN32.exe. When each module is opened or other windows within Sage open, another instance of PVXWIN32.exe is opened. I found that the zero trust software (ThreatLocker) would allow the initial PVXWIN32.exe process to run and spay the window, but then it was preventing the additional windows from displaying the screen, and here is where it gets strange. ThreatLocker's primary function is to stop apps that have not been pre-approved from running. In this case, it's letting PVXWIN32.exe run and that's how we are getting Sage 100 started and logged into. Then, it's allowing the PVXWIN32.exe process that is started with opening a module but just not allowing it to display the window, something ThreatLocker has never done before. First issue is PVXWIN32.exe is already allowed and is already running. Second issue, ThreatLocker is actually allowing the second or third instance of PVXWIN32.exe to run in the background, but won't let the display of the window to occur, this is something we have never seen and technically it should be happening to everyone at CLC as they are all running ThreatLocker and using the same set of app policies as the policies are managed per customer and applied to all machines at that location. I'm going to have to open a ticket with the ThreatLocker support team tomorrow to get to the bottom of this issue. I'll update you in the morning.

Sooo...  The IT guy SAID that he had uninstalled the security software and tested.  I just got this from him, bearing in mind that when after Scott's review we suggested uninstalling the security software he said "everyone wants to blame the security software.."

I believe I found the cause of the issue but I am unable to explain why it's happening. As you know, the process that runs when starting Sage 100 is called PVXWIN32.exe. When each module is opened or other windows within Sage open, another instance of PVXWIN32.exe is opened. I found that the zero trust software (ThreatLocker) would allow the initial PVXWIN32.exe process to run and spay the window, but then it was preventing the additional windows from displaying the screen, and here is where it gets strange. ThreatLocker's primary function is to stop apps that have not been pre-approved from running. In this case, it's letting PVXWIN32.exe run and that's how we are getting Sage 100 started and logged into. Then, it's allowing the PVXWIN32.exe process that is started with opening a module but just not allowing it to display the window, something ThreatLocker has never done before. First issue is PVXWIN32.exe is already allowed and is already running. Second issue, ThreatLocker is actually allowing the second or third instance of PVXWIN32.exe to run in the background, but won't let the display of the window to occur, this is something we have never seen and technically it should be happening to everyone at CLC as they are all running ThreatLocker and using the same set of app policies as the policies are managed per customer and applied to all machines at that location. I'm going to have to open a ticket with the ThreatLocker support team tomorrow to get to the bottom of this issue. I'll update you in the morning.