Windows Security Update 5094126 Access Violation in Pinupmenu.exe...

[mkarasek]

Did a W11 Update today 6/10, Security Update 5094126.

After this trying to launch pinup popper (pinupmenu.exe) caused access violation.   
Uninstalled this update and all is back to normal.

It looks like in a different thread the Windows Advanced Update (if you have this turned on) is causing the same problem..

Would advise to NOT do any W11 Updates until this gets straightened out. 

[mkarasek]

Looks like Nailbuster has provided a  fix for this:

https://www.nailbuster.com/wikipinup/doku.php?id=win11-fix

 

 

[elevinn]

darn, the nailbuster fix didnt work for me and my windows wont allow me to roll back

 

[Truest1]

14 hours ago, elevinn said:

darn, the nailbuster fix didnt work for me and my windows wont allow me to roll back

 

Yup same here. I had to install window 11 fresh install and not download that update. 

[mkarasek]

Just got he june update and nailbuster fix worked.  Make sure you run the script as admin.

[elevinn]

7 hours ago, mkarasek said:

Just got he june update and nailbuster fix worked.  Make sure you run the script as admin.

yeah followed the instructions and ran as admin. no go. ah well, i guess i'll do a fresh windows 11 install

[sushko]

The fix worked great for me!!!

[jupiters]

TLDR; after ridiculous amount of hours finding and fixing this bug so I could post the solution here, if I had just been patient and let the experts tackle it, I could've used Nailbuster's patch and gotten more sleep.  

 

No need to read below, just follow the links above to Nailbuster's patch for the more thorough fix.

 

If you're curious, here's my documentation and solution:

The confirmed triggering update is KB5094126 (OS Build 26200.8655), the 2026-06 Cumulative Security Update for Windows 11 25H2. We have not tested whether earlier or later cumulative updates carry the same defect, only that this specific update reliably reproduces it.

 

Error:

Server execution failed, ClassID: {88919FAC-00B2-4AA8-B1C7-52AD65C476D3}

This ClassID corresponds to the PinUP Player COM Object used by Popper to launch and render its frontend window.

 

Related Cascading Errors: 

After the initial COM error is dismissed, PinUpMenu.exe may also throw access violation errors as it continues trying to initialize without a valid COM interface, for example:

- Access violation at address 009045EA in module 'PinUpMenu.exe'. Read of address 00000014.

- Access violation at address 009035D7 in module 'PinUpMenu.exe'. Write of address 00000070.

These are downstream symptoms of the same broken COM registration. PinUpMenu.exe dereferencing a null/invalid pointer where the PinUP Player COM interface should be, not independent defects. Including them here so the report is discoverable by anyone searching on these access-violation strings specifically.

 

Root Cause is in the Registry:

HKLM\SOFTWARE\WOW6432Node\Classes\AppID\{88919FAC-00B2-4AA8-B1C7-52AD65C476D3} contains a DllSurrogate value that is present but empty rather than absent. Confirmed on two separate machines: the broken empty DllSurrogate value appears specifically in the WOW6432Node branch; the non-WOW6432Node branch (HKLM\SOFTWARE\Classes\AppID\{same GUID}) simply lacks a DllSurrogate value entirely on both machines, which is expected and not part of the defect. Per Windows COM semantics, an empty (not missing) DllSurrogate value instructs the OS to host the COM server via DLL surrogate (dllhost.exe) rather than launching it directly via LocalServer32. Since PinUpPlayer is an EXE-based COM server, this hosting mode is incompatible, and launch fails with the "Server execution failed" error reported against the ClassID, even though the actual defect is in the AppID entry, not the CLSID/class registration itself.

 

My Fix / Workaround:

1) Open Registry Editor (regedit.exe), navigate to: HKLM\SOFTWARE\WOW6432Node\Classes\AppID\{88919FAC-00B2-4AA8-B1C7-52AD65C476D3}

2) Delete the empty DllSurrogate value.

3) Set (Default) to PinUP Player Com Object.

4) Reboot.

5) Launch Popper. resolves immediately.

 

 

Edited July 3 by jupiters

[NailBuster]

2 hours ago, jupiters said:

 

 

Message to Nailbuster: Claude suggests maybe the installer itself can be hardened to explicitly set DllSurrogate as absent (not empty) at install time, in case that's what makes it vulnerable to being zeroed out by a Windows Update servicing pass.

 

 

I think its great you are trying to help,  but please stop spamming your "solution everywhere" on different threads.  As you stated you "don't know what my fix does".....  Because the current fix on my wiki is more complete than your AI Solution.  Its been downloaded and used many hundreds of times and confirmed to be a good solution.  (it is a registry fix as well).

Edited July 3 by NailBuster

[jupiters]

1 hour ago, NailBuster said:

 

I think its great you are trying to help,  but please stop spamming your "solution everywhere" on different threads.  As you stated you "don't know what my fix does".....  Because the current fix on my wiki is more complete than your AI Solution.  Its been downloaded and used many hundreds of times and confirmed to be a good solution.  (it is a registry fix as well).

You're absolutely right NailBuster. I was just trying to help, especially since I'd put so much time into this bug was trying to save others the same pain. Thank you for removing my other posts/links to my solution above. I would delete my entire post but seems it helps with documentation and maybe provides valuable strings to find in a search. I've also shortened and updated my post with a TLDR heading that says to just use your patch, and ignore my below fix. Next time I'll leave the fixing to the experts/author.

 

We all really appreciate your huge contribution to the community!! Thank you for everything.

[Truest1]

On 7/2/2026 at 6:19 PM, jupiters said:

TLDR; after ridiculous amount of hours finding and fixing this bug so I could post the solution here, if I had just been patient and let the experts tackle it, I could've used Nailbuster's patch and gotten more sleep.  

 

No need to read below, just follow the links above to Nailbuster's patch for the more thorough fix.

 

If you're curious, here's my documentation and solution:

The confirmed triggering update is KB5094126 (OS Build 26200.8655), the 2026-06 Cumulative Security Update for Windows 11 25H2. We have not tested whether earlier or later cumulative updates carry the same defect, only that this specific update reliably reproduces it.

 

Error:

Server execution failed, ClassID: {88919FAC-00B2-4AA8-B1C7-52AD65C476D3}

This ClassID corresponds to the PinUP Player COM Object used by Popper to launch and render its frontend window.

 

Related Cascading Errors: 

After the initial COM error is dismissed, PinUpMenu.exe may also throw access violation errors as it continues trying to initialize without a valid COM interface, for example:

- Access violation at address 009045EA in module 'PinUpMenu.exe'. Read of address 00000014.

- Access violation at address 009035D7 in module 'PinUpMenu.exe'. Write of address 00000070.

These are downstream symptoms of the same broken COM registration. PinUpMenu.exe dereferencing a null/invalid pointer where the PinUP Player COM interface should be, not independent defects. Including them here so the report is discoverable by anyone searching on these access-violation strings specifically.

 

Root Cause is in the Registry:

HKLM\SOFTWARE\WOW6432Node\Classes\AppID\{88919FAC-00B2-4AA8-B1C7-52AD65C476D3} contains a DllSurrogate value that is present but empty rather than absent. Confirmed on two separate machines: the broken empty DllSurrogate value appears specifically in the WOW6432Node branch; the non-WOW6432Node branch (HKLM\SOFTWARE\Classes\AppID\{same GUID}) simply lacks a DllSurrogate value entirely on both machines, which is expected and not part of the defect. Per Windows COM semantics, an empty (not missing) DllSurrogate value instructs the OS to host the COM server via DLL surrogate (dllhost.exe) rather than launching it directly via LocalServer32. Since PinUpPlayer is an EXE-based COM server, this hosting mode is incompatible, and launch fails with the "Server execution failed" error reported against the ClassID, even though the actual defect is in the AppID entry, not the CLSID/class registration itself.

 

My Fix / Workaround:

1) Open Registry Editor (regedit.exe), navigate to: HKLM\SOFTWARE\WOW6432Node\Classes\AppID\{88919FAC-00B2-4AA8-B1C7-52AD65C476D3}

2) Delete the empty DllSurrogate value.

3) Set (Default) to PinUP Player Com Object.

4) Reboot.

5) Launch Popper. resolves immediately.

 

 

Thank you for posting this Jupiters i will try this since the one from nailbuster didn't seem to work for me. it did but next time i rebooted by pc the pup tables started CRASHING AGAIN.

I have went back to windows 10 because of this . I'm scared to reinstall windows 11 and try your workaround since i have my windows 10 build working great at the moment lol.