Microsoft XPS Document Writer Download for Windows 10

Anonymous
2018-05-18T19:03:20+00:00

A combination of a recent Windows update and Quickbooks update has left us without the XPS Document Writer, which is necessary to save or print invoices from Quickbooks.

The XPS Document Writer is not an option when trying to install a new printer and neither the XPS Service nor XPS Viewer are options listed in "Turn Windows features on or off."  I suspect we need to reinstall the Writer, but I'm unable to locate a version for Windows 10. 

We have already tried a system restore, but this failed to resolve the issue.

The only link I have found: https://www.microsoft.com/en-us/download/details.aspx?id=11816 is not compatible with Windows 10.

Where can I locate the XPS Document Writer for Windows 10?

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2018-05-18T19:24:18+00:00

Hi Katherine,

Hit Windows key + R together, enter: optionalfeatures

Just check once more to see if the "Microsoft XPS Document Writer" exists, at least it pops up on my Windows 10 with 1803. Check that if not already, click OK. Now we need to bring back the XPS Viewer.

Go to Start, look for "Apps & features", then click that. In the new window under Apps & features, click Manage optional features. Click "Add a feature", then look for XPS Viewer, and click the Install button that pops up.

If this doesn't work at all, please provide me with your Windows 10 edition (Home, Pro, Enterprise), and I can look into this further for you.

Let me know.

Was this answer helpful?

300+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2019-06-14T01:59:23+00:00

>>Found this link - worked for me! Allowed me to reinstall XPS Document Writer.<<

https://superuser.com/questions/1192920/how-to-force-xps-service-installation-on-windows-10

This worked perfectly for me. Downloaded the zip file and followed the KB instructions. Worth repeating here:

File download found here -- just click download: https://drive.google.com/file/d/0B8Zv87UX9gSKLV9ud3c1ZFAtcjA/view

Instructions: I followed them with following exceptions -- ignore Windows 7, worked for Windows 10. I could not remove the XPS printer because it was not there. I just ignored that and went to Add printer. All else I followed and XPS was installed.

How to resolve PDF issues on windows 8?

On Windows 8 Emailing forms, previous bank reconciliation reports, and saving as PDF within the program may get resolved by the following Steps:

  1. Download and extract the Windows 7 XPS document writer printer drivers containing folder from here Microsoft XPS Document Writer Click File and Download.
  2. Copy and paste this folder to C Drive\Windows\System32.
  3. Open Devices and Printers using Windows key+ R to get the run box and type Control.exe Printers and press Enter.
  4. Right Click Microsoft XPS Document Writer and Click Remove Device.
  5. Click Add a new printer and Click on “A printer that wasn’t listed”
  6. Select “add local printer with manual settings” and Click next.
  7. Select the radio button Create a new Port,Type of port Local port and Click next.
  8. Enter a port as XPS and click ok.
  9. Click have disk and Browse to the C Drive\Windows\System32\Microsoft XPS Document Writer
  10. Select prnms001 file and click open and the ok.
  11. Select replace Current drivers and next.
  12. Type a printer name will show up as Microsoft XPS Document Writer just click next and Finish.

Test: Open Quickbooks and open any invoice and Click File and Save as PDF and save to the desktop and check if that invoice got saved as PDF.

Was this answer helpful?

200+ people found this answer helpful.
0 comments No comments

150 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-11-08T17:32:29+00:00

    2018-11-07 13:19:01, Info                  CSI    00000025 IsSpoolerRunning: The spooler is 'Running'.

    What about trying to change that detail?

    In case it helps here's what I have for MXDW

    PS>LS -RE -Fi *MXDW* -Fo -EA:SilentlyContinue sort LastWriteTime ft Length,FullName -AutoSize<br><br><br>Length FullName <br><br> ------ -------- <br><br> 907264 C:\Windows\System32\spool\drivers\x64{FF82869D-F1A2-47FC-A9F9-CB657670DD69}\MXDWDRV.DLL <br><br>1029632 C:\Windows\System32\spool\drivers\W32X86{57765DDC-228C-4DA1-AA44-648E83761496}\MXDWDRV.DLL <br><br> 908800 C:\Windows\System32\spool\drivers\x64{17A23850-7432-4CE4-98A7-9B7CFF8E9F9C}\MXDWDRV.DLL <br><br> 908800 C:\Windows\System32\spool\drivers\x64{79095006-3425-43E8-85B1-66C7219064B7}\MXDWDRV.DLL <br><br>1030656 C:\Windows\System32\spool\drivers\W32X86{469EAE2D-63FB-47FE-990E-63FE20463354}\MXDWDRV.DLL <br><br>1030656 C:\Windows\System32\spool\drivers\W32X86{E17C2E3B-C190-4252-AFD9-1C472F625239}\MXDWDRV.DLL <br><br>1030656 C:\Windows\System32\spool\drivers\W32X86{FE0B948A-CF64-4045-A92D-60967048226C}\MXDWDRV.DLL <br><br> 901120 C:\Windows\System32\spool\drivers\x64{129C2A83-04F8-43DC-BE63-3B56CA42983B}\MXDWDRV.DLL <br><br> 901120 C:\Windows\System32\spool\drivers\x64{AE3DCA3A-9E4C-4725-94C7-0B78F69608FF}\MXDWDRV.DLL <br><br>   3072 C:\Windows\WinSxS\amd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_10.0.17134.1_none_08592b41cc30af9b\mxdwdui.dll <br><br>     12 C:\Windows\System32\DriverStore\FileRepository\prnms001.inf_amd64_cb0feabdd71f0e97\MXDW-pipelineconfig.xml <br><br>     12 C:\Windows\System32\spool\tools\Microsoft XPS Document Writer\mxdw-pipelineconfig.xml <br><br>     12 C:\Windows\WinSxS\amd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_10.0.17134.1_none_08592b41cc30af9b\mxdw-pipelineconfig.xml <br><br>   3072 C:\Windows\System32\DriverStore\FileRepository\prnms001.inf_amd64_cb0feabdd71f0e97\mxdwdui.dll <br><br>   3072 C:\Windows\System32\spool\tools\Microsoft XPS Document Writer\mxdwdui.dll <br><br>  67634 C:\Windows\WinSxS\amd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_10.0.17134.1_none_08592b41cc30af9b\mxdw.gpd <br><br>  67634 C:\Windows\System32\spool\tools\Microsoft XPS Document Writer\mxdw.gpd <br><br>    353 C:\Windows\System32\spool\tools\Microsoft XPS Document Writer\mxdw-manifest.ini <br><br>  67634 C:\Windows\System32\DriverStore\FileRepository\prnms001.inf_amd64_cb0feabdd71f0e97\MXDW.gpd <br><br>    353 C:\Windows\System32\DriverStore\FileRepository\prnms001.inf_amd64_cb0feabdd71f0e97\MXDW-manifest.ini <br><br>    353 C:\Windows\WinSxS\amd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_10.0.17134.1_none_08592b41cc30af9b\mxdw-manifest.ini <br><br>1016832 C:\Windows\WinSxS\x86_dual_ntprint.inf_31bf3856ad364e35_10.0.17134.191_none_6a6f5435e7754b67\I386\MXDWDRV.DLL <br><br>1016832 C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_x86_318eda08781bddd7\I386\MXDWDRV.DLL <br><br>1016832 C:\Windows\System32\spool\drivers\W32X86\3\mxdwdrv.dll <br><br> 876544 C:\Windows\System32\spool\drivers\x64\3\MXDWDRV.DLL <br><br> 876544 C:\Windows\WinSxS\amd64_dual_ntprint.inf_31bf3856ad364e35_10.0.17134.191_none_c68defb99fd2bc9d\Amd64\MXDWDRV.DLL <br><br> 876544 C:\Windows\System32\DriverStore\FileRepository\ntprint.inf_amd64_318eda08781bddd7\Amd64\MXDWDRV.DLL <br><br>  13191 C:\Windows\WinSxS\amd64_dual_ntprint.inf_31bf3856ad364e35_10.0.17134.1_none_ca9e3e01b2be3b63\Amd64\MXDWDRV.DLL <br><br>  24650 C:\Windows\WinSxS\x86_dual_ntprint.inf_31bf3856ad364e35_10.0.17134.1_none_6e7fa27dfa60ca2d\I386\MXDWDRV.DLL

    I don't know exactly where to check for print queues.  My guess would be something to do with the Spooler but I'm not finding anything useful for diagnosing problems with it.  Otherwise I think a potentially useful tack would be to use WMIC to check on PrinterConfig and PrintJob.  FWIW I do have something strange showing with PrintJob List Full  (first did List Brief to see I only had 2 items).  Both say Microsoft Print to PDF but then (in the List Full) say "PrintProcessor=MS_XPS_PROC".  I also tried this one 

        printerconfig where (Caption like "%XPS%") get /format:list

    but imagine it would only be useful if it resulted in an error.

    On the driver side compare what PowerShell

        Get-Printer  |?  Name -match "XPS"  |  fl *

    and WMIC

        printer where (Name like "%XPS%") get /format:list

    show.  Both refer to  PrintProcessor=winprint  which looks different from that  MS_XPS_PROC that the other query brought out.

    HTH

    Robert


    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-11-08T13:51:32+00:00

    Reverse engineering. I used to say I was a "hacker" before that term meant something else. By hacker I meant it took me three days of hacking to find the 3-minute solution if someone had simply told me three days earlier. But, this problem has been far more elusive.

    The CBS log has the following clues in regards to the XPS Document Writer:

    2018-11-07 13:19:01, Info                  CSI    00000023 Performing 1 operations as follows:

      (0)  LockComponentPath: flags: 0 comp: {l:16 b:366ae75bc676d40119000000e82d043b} pathid: {l:16 b:366ae75bc676d4011a000000e82d043b} path: [l:117]'\SystemRoot\WinSxS\amd64_microsoft-windows-p..g-xpsdocumentwriter_31bf3856ad364e35_10.0.17134.1_none_08592b41cc30af9b' pid: 2de8 starttime: 131860882890027435

    2018-11-07 13:19:01, Info                  CSI    00000024 Setup MXDW AI Installation Called Online.

    2018-11-07 13:19:01, Info                  CSI    00000025 IsSpoolerRunning: The spooler is 'Running'.

    2018-11-07 13:19:01, Info                  CSI    00000026 SetupMxdwAI: IsMxdwPrintDriverInstalled(): The MXDW Print Driver is 'INSTALLED'

    2018-11-07 13:19:01, Info                  CSI    00000027 SetupMxdwAI: IsMxdwPrintQueueInstalled(): The MXDW Print Queue is 'NOT INSTALLED'

    2018-11-07 13:19:01, Error                 CSI    00000028 (F) SetupMxdwAI: InstallMxdwPrintQueue(): ::AddPrinter() FAILED!

    [gle=0x80004005]

    2018-11-07 13:19:01, Error                 CSI    00000029@2018/11/7:18:19:01.901 (F) base\wcp\plugins\printadvancedinstaller\dll\setupmxdwai.cpp(337): Error HRESULT_FROM_WIN32(ERROR_INVALID_HANDLE) originated in function Windows::WCP::SetupMxdwAI::InstallMxdwPrintQueue expression: GetLastError

    [gle=0x80004005]

    I have no idea why the MXDW Print Queue was not installed, but that seems to be the point of failure.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-11-08T12:39:26+00:00

    Scanning the DISM log showed no entries of XPS. Scanning the CBS log had 131 XPS entries. Many seemed to be repeats, but there were at least a couple that went something like this: "Error Failed execution of queue item Installer: Setup Microsoft XPS Document Writer Installer with HRESULT  HRESULT_FROM_WIN32(ERROR_INVALID_HANDLE). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable."

    As expected, nothing useful in the log we are shown but something useful in CBS.log.  Notice the timestamps will correspond with times when you were trying to do something with it.  There will be references to files in the WinSxS that are corrupt or missing.

    On PowerShell I get FeatureName: Printing-XPSServices-Features as Disabled, and Microsoft-Windows-Printing-XPSServices-Package as Enabled.

    I have both enabled.   There is only one explicit XPS feature in Optional Features.   I do have some Print and Document Services enabled but I don't know if any of them would be related to the one you have disabled.  I do have the option to uninstall XPS Viewer in Manage Optional Features.  Also I remember once having to remove all printing support in order to get a cumulative update done in preview but can't remember the details, except that I vaguely recall being unable to do anything about remote print queues.  If you can't figure out what the CBS.log entries may be implying but you have some of those causing a problem you may have to do something with them.  Who knows?  No source and no support documentation = reverse engineering.

    Good luck

    Robert


    Was this answer helpful?

    0 comments No comments