Skip go content

splwow64.exe

Windows ProcessMicrosoft Corporation

Catalog search terms splwow64, spooler wow64, 32-bit print thunk

WindowsSystem Component

Print driver host for 32-bit applications on top 64-bit Windows. Na di thunk wey dey let 32-bit app talk to 64-bit print drivers. spoolsv.exe na di Print Spooler.

Wetin you need know

splwow64 na di 32-bit print thunk, no be di spooler.

splwow64.exe dey exist make 32-bit program fit print on top 64-bit Windows. Di Print Spooler service still dey live inside spoolsv.exe. PrintIsolationHost.exe dey isolate drivers. To end di thunk no dey empty di queue folder.

E safe?
Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
Na di spooler?
No. spoolsv na di spooler
Wetin make am dey here?
One 32-bit app print
Feex tok say
If splwow64 remain after I close 32-bit Office, I dey check whether dat app still hold di printer. I no dey restart di whole spooler as my first action unless jobs don stuck inside spoolsv.

Wetin be splwow64.exe?

splwow64.exe na di 32-bit print thunk on top 64-bit Windows. 32-bit app no fit load 64-bit print driver directly, so dis host dey bridge am. E no be spoolsv.exe, di Print Spooler process.

Wetin e dey do?

E dey translate print calls from 32-bit apps. Di queue, port monitors, and service still belong to spoolsv.exe. To isolate bad driver na work of PrintIsolationHost.exe.

Wetin make am dey run?

32-bit Word, browser, abi CAD program print or open printer properties. Di thunk fit stay small time after di last 32-bit print. 64-bit-only PC wey no dey ever print from 32-bit apps fit rarely show am.

Inspect the running instance

Inside Windows PowerShell, this read-only query show matching process IDs, creation times and executable paths on this PC. (pcm)

Get-CimInstance -ClassName Win32_Process | Where-Object { $_.Name -eq 'splwow64.exe' } | Select-Object ProcessId, ParentProcessId, CreationDate, Name, ExecutablePath | Format-List

No result or a path we no fit access is inconclusive. Protected processes fit restrict access, and process IDs fit be reused. Keep personal paths local. (pcm)

Use the file-identity guide to compare signatures and product metadata. A filename alone no fit establish safety. (pcm)

E dey safe?

Check dis running file

System32 splwow64.exe na di Microsoft thunk. splwow64.exe inside "printer crack" folder no be am. Dis file still no be di spooler.

Compare the recorded location with the actual file. A familiar folder alone no fit establish identity. (pcm)

C:\Windows\System32\splwow64.exe

  • 64-bit Windows only
  • Triggered by 32-bit print clients
  • Spooler process: spoolsv.exe

I fit end am?

Dat 32-bit print session go die

To end splwow64.exe dey drop di thunk. Jobs wey already dey inside spooler go stay inside spoolsv.exe. Clear PRINTERS only after you don stop di Spooler service, no be to end only dis host.

I fit comot am?

No

No delete splwow64.exe. 32-bit apps no go fit print. Disable di Print Spooler only if you agree say no local printing at all. Dat decision na about spoolsv, no be dis thunk.

E suppose start with Windows?

32-bit print dey start am. E no be Startup Apps checkbox.

Measure resource use

Measure the current process rather than assume a universal baseline
CPU and memory Compare several observations for the same PID and workload. This entry get no independently measured universal baseline. (pcm)
Disk and network Attribute activity to the actual process and current task; a filename alone no fit establish expected destinations or transfer volume. (pcm)

File information

splwow64.exe file information
Executable name splwow64.exe
Recorded installation path C:\Windows\System32\splwow64.exe
Publisher Microsoft Corporation
Signature check Inspect the actual file; this entry no dey certify its certificate identity. (pcm)

Common wahala dem

Thunk no dey ever exit

32-bit app still get printer DC open. Close dat app. If di queue jam, na spoolsv and di PRINTERS folder be dat.

People dey disable Spooler to stop splwow64

Dat one go still kill 64-bit printing. End di 32-bit client first.

How to troubleshoot

Diagnose before you change anything wey fit scatter things.

Name di 32-bit app wey print

Task Manager command line and di last program wey show print dialog. 64-bit Notepad no need dis thunk.

Jobs wey stuck: treat spoolsv, no be di thunk

Stop Spooler, clear System32\spool\PRINTERS, start Spooler. To end only splwow64 go leave di queue files.

Technical details

Technical details
splwow64.exe technical details
Image name splwow64.exe
Role 32-bit print driver thunk on top 64-bit Windows

Check the identity of running file

A filename alone no fit establish safety. Verify the actual path, signature and product identity. (pcm)

Sources and verification

Recorded source label: August 2026. Dis label no establish independent verification. How we dey do research.

Dis article make sense to you?

Yes or no dey enough. Choose reason if you want, or add short note.

Dis article make sense to you?