Windows 10: Issues with splwow64.exe

I am running an App based on ArcGis, V10. When I try to print any document over its own virtual printer, the dialog box of splwow64.exe goes background. I press Alt+Tab keys, Ctrl+Tab, I pray to the gods, but the result is the same, nothing to do. Only, I can access to the dialog box if I change the screen resolution. Then, the dialog emerges foreground, but dead, just a like a picture. And the program remains locked.

My PC has a W10 Pro Version 2004 OSVersion 19041.630 with a version of splwow64.exe #10.19041.388 of 7/15/2020.

But a I have another PC with W10 Home version, with a version of splwow64.exe #10.17134.1130 of 11/8/2019.

When I command the same print job in this computer with the same program, It runs correctly, like a shot, and I can finish my job.

My question is, Can I replace the file?, Is this convenient? and What do I have to do for this?. Being an important Windows component, I supose that it must be protected.

I have bought my computer just for working, and the other one is just for other things.

Thanks.

:)

 

Windows 10 Upgrade - splwow64.exe

I updated multiple computers from Windows 7 Pro to Windows 10 Pro (x86 and x64) this week. The number problems that occurred are baffling but I finally got control of most my issues. However, one issue regarding splwow64.exe is messing up our printing.

The following is what I figured out after significant research and fix attempts:

splwow64.exe is ran under Anonymous-Login

splwow64.exe is initiated by spooler.exe for x86 to x64 printing compatibility

Anonymous-Logon prevents application from printing due to Anonymous-Logon having insufficient rights.

Application works correctly if I forcefully close splwow64.exe and run splwow64.exe under the local account (LIKE IT SHOULD)

WHYYYY is spooler.exe creating splwow64.exe under Anonymous-Logon??????????? This is not a singular issue. Its occurring on at least 4 computers.

 

Windows 10 Upgrade - splwow64.exe

1. There is no error code. The print job just doesn't start.

2. No

3. Not limited to particular formats.

I have finally been able to replicate this issue. I use a pdf printing program to collect print jobs from multiple apps. I have one app (app1) that causes the print job to printed under anonymous_logon and another (app2) that prints under the current user
account. If splwow64.exe starts under current user account due to app2 and then used by app1, splwow64.exe works. However, if app1 starts it under anonymous logon and app2 attempts to print out, splwow64.exe fails. I have confirmed this issue effects regular
printers as well since splwow64.exe runs at least 2 mins (by default) or as long as the app that started splwow64.exe is running.

I also have confirmed that giving anonymous_logon read/execute rights does not resolve the issue.

I also found and posted on another post regarding this unresolved issue: SplWOW64.exe is freezing up 32bit programs and halting printing on 64bit Windows 7

Does anyone know how to force splwow64.exe to always run under the current user account?

Also, in a terminal setting (like windows server 2012), would each account have its own splwow64.exe?

-----------

Also, Vinodh's edits to his post doesn't alert me via email.

 

Word 64bit wants to print under splwow64.exe

Then the question is: Why does Word 64bit need it to print to a 64bit printer driver on 64bit Windows machine?

The other Office apps like Excel and PowerPoint don't use splwow64.exe.

Actually, we do need the Print Spooler service.