steam_master_ipc_name_override environment variable breaks Electron apps (VS Code, Claude Code)

[BigFancyBen]

Description

I'm (sorry) not 100% sure how to reproduce, but here's what was amiss on my system.

When "Isolate Steam" is enabled, Duo sets the steam_master_ipc_name_override environment variable globally with a corrupted value, which breaks Electron-based applications.

Error message

The property 'options.env['steam_master_ipc_name_override']' must be a string without null bytes. Received 'Console\x00'

Affected apps

• VS Code
• Claude Code
• Likely any Electron app

Environment

• Duo version:
• Windows version:

Steps to reproduce

1. Enable "Isolate Steam" in Duo Manager
2. Reboot
3. Open a new command prompt on the host session
4. Run code or any Electron app

Expected behavior

The environment variable should either:

• Not be set on the host/Console session (only on Duo instances)
• Not contain null bytes

Workaround

Disable "Isolate Steam" in Duo Manager and reboot.

[mad0x20wizard]

@BigFancyBen Have you found out, what the problem was? Seems like this wasn't the first time someone encountered this.

[BigFancyBen]

it seemed like the bad character in the registry value caused a ripple of negative effects. the only way I was able to fix it was by turning the steam isolation off.

I tried regedit and a variety of things Claude code suggested might help ubbork the value, but nothing worked.

I had also set up goldberg for steam and nucleus co-op, so I had a bunch of moving parts.

I'm not at all confident I could recreate the bug is why I decided to resolve this issue.

[117649]

Have the same problem. Enable "Isolate Steam" again and it reappear.

You shouldn't close this as it not been fixed.

[tvdoesstuff]

Hello! I'm not sure if I can talk with you Guys but I haven't used Duo in like a year and a half but that error now crept up on me even though I haven't had it installed for a while... Wanted to install openclaw but it and npm keep giving me the error : npm error The property 'options.env['steam_master_ipc_name_override']' must be a string without null bytes. Received 'Console\x00'

I've been trying to change its value but no matter what I try it keeps on changing itself to "Console" in the Process level. Duo also won't allow me to deactivate saying "It's only for paying people" so I'm just stuck here screwed and probably need to factory reset my PC...

[mad0x20wizard]

Hey @tvdoesstuff. Did you update to the latest version of Duo (1.5.7) or are you still on one of the earlier builds? What exactly do you mean when you say it won't allow you to deactivate? Shouldn't you have been prevented then from activating it in the first place?

Please do a quick check for me and see which version of the verifier.dll is currently in your System32 directory:

[tvdoesstuff]

It says "1.5.6.0"

And I Don't know, the switch is turned on but darkend and hovering over says this:

[mad0x20wizard]

The tooltip is misleading here and probably belongs to another setting/button. The facility for Process Patching changed since your last installation, so it wouldn't deactivate it properly anyway.

What I can say with confidence is, that you still have a leftover file from the 1.5.6 installation, which gets injected into processes without actual necessity and leads to the problem. Do you, by any change, see a backup file residing next to the verifier.dll in the System32 directory, that has approximately the signature of the file I showed you?

If you have it, try to replace the "Duo Application Verifier" with the original file. If it cannot be deleted, because of file locks, try using System Informer to find programs that have an open handle to the .dll and close them. You should then be able to replace the custom verifier with Windows own version.

[tvdoesstuff]

There is only a "verifier.dll.bak" File but it Doesn't list any verison numbers in Property.

[mad0x20wizard]

Place it on your Desktop and rename it to .dll, so that Windows shows you it's properties.

[tvdoesstuff]

[mad0x20wizard]

Yeah, this is the original file. Can you just copy it now to the System32 directory, so that it overwrites the existing file there?

[tvdoesstuff]

Keine Bereichtigungen... auch nicht nach Administrator-Ausführung

[mad0x20wizard]

This is because the library is still loaded and in use by some application. There are two possible solutions to this:

1. Use a software like System Informer to find the open handles to it and close them (or the application). Start it as administrator and use the function "Find handles or DLLs..." in the System menu. There search for "verifier" to find all programs with open handles for it. Since you cannot close the handle directly, go to the process and terminate it.
2. Alternatively you can open regedit.exe and open the key Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options. There you will find subkeys for various programs. Some of them will have the value GlobalFlag set to 0x100. You have to remove all of these GlobalFlag entries and after that reboot your system. The verifier.dll should now be free to be replaced by the original one from the backup.
3. There is also another way, maybe simpler depending on your experiences: Boot the PC in recovery mode. In this state nothing will prevent you from replacing the file, using the integrated command line tool. I cannot guide you through this, though.

Either way, once you managed to replace the verifier.dll with the original one, your problem should be gone.