XPS Document Writer fails on Server 2016

%3CLINGO-SUB%20id%3D%22lingo-sub-2647133%22%20slang%3D%22en-US%22%3EXPS%20Document%20Writer%20fails%20on%20Server%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2647133%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20copy%20of%20Windows%20Server%202016%20running%20as%20a%20VM%20on%20a%20Dell%20PowerEdge%20with%20VMWare.%20This%20server%20is%20set%20up%20to%20be%20an%20application%20server%2C%20hosting%20QuickBooks%20Enterprise%202021.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20few%20weeks%20ago%20QuickBooks%20was%20suddenly%20unable%20to%20generate%20PDFs.%20After%20troubleshooting%20the%20cause%20it%20turns%20out%20that%20the%20XPS%20Document%20Writer%20had%20disappeared.%20The%20driver%20for%20the%20MXDW%20is%20still%20installed%20in%20the%20system.%20I%20cannot%20get%20the%20server%20to%20actually%20install%20a%20printer%20using%20that%20driver%2C%20which%20QuickBooks%20needs%20to%20generate%20PDFs.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EWhen%20attempting%20to%20install%20the%20printer%20manually%20with%20the%20Add%20Printer%20Wizard%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26gt%3BAdd%20a%20local%20printer%20with%20manual%20settings%3C%2FP%3E%3CP%3E%26gt%3BUse%20an%20existing%20port%20-%20PORTPROMPT%3A%20(Local%20Port)%3C%2FP%3E%3CP%3E%26gt%3BSelect%20driver%20%22Microsoft%20XPS%20Document%20Writer%20v4%22%3C%2FP%3E%3CP%3E**%3CSTRONG%3ENOTE%3A%3C%2FSTRONG%3E%20Have%20done%20this%20from%20Windows%20Update%2C%20and%20also%20selecting%20the%20actual%20driver%20from%20the%20driver%20store%20by%20selecting%20%22have%20disk%22**%3C%2FP%3E%3CP%3E%26gt%3BTwo%20different%20errors%20are%20generated%20depending%20on%20what%20is%20selected%20next%3A%3C%2FP%3E%3CP%3E%26gt%3B%26gt%3BUse%20the%20driver%20that%20is%20currently%20installed%20-%20ERROR%20%22Unable%20to%20install%20printer.%20The%20handle%20is%20invalid%22%3C%2FP%3E%3CP%3E%26gt%3B%26gt%3BReplace%20the%20current%20driver%20-%20ERROR%20%22Printer%20driver%20was%20not%20installed.%20Element%20not%20found.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EWhen%20attempting%20to%20install%20the%20printer%20through%20the%20Print%20Management%20interface%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26gt%3BRight%20click%20%22Printers%22%20under%20SERVER%2C%20select%20%22Add%20Printer%22%3C%2FP%3E%3CP%3E%26gt%3BAdd%20a%20new%20printer%20using%20an%20existing%20port%3A%20PORTPROMPT%3A%20(Local%20Port)%3C%2FP%3E%3CP%3E%26gt%3BUse%20an%20existing%20printer%20driver%20on%20the%20computer%20-%20select%20from%20dropdown%20menu%20-%20%22Microsoft%20XPS%20Document%20Writer%20v4%22%3C%2FP%3E%3CP%3E%26gt%3BPrinter%20Name%20-%20%22Microsoft%20XPS%20Document%20Writer%20v4%22%3C%2FP%3E%3CP%3E%26gt%3BERROR%20-%20Unable%20to%20install%20printer.%20The%20handle%20is%20invalid.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ESteps%20tried%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EStep%20-%20sfc%20%2Fscannow%3C%2FP%3E%3CP%3EResult%20-%26nbsp%3B%3C%2FP%3E%3CP%3EBeginning%20system%20scan.%20This%20process%20will%20take%20some%20time.%3C%2FP%3E%3CP%3EBeginning%20verification%20phase%20of%20system%20scan.%3CBR%20%2F%3EVerification%20100%25%20complete.%3C%2FP%3E%3CP%3EWindows%20Resource%20Protection%20found%20corrupt%20files%20but%20was%20unable%20to%20fix%20some%3CBR%20%2F%3Eof%20them.%20Details%20are%20included%20in%20the%20CBS.Log%20windir%5CLogs%5CCBS%5CCBS.log.%20For%3CBR%20%2F%3Eexample%20C%3A%5CWindows%5CLogs%5CCBS%5CCBS.log.%20Note%20that%20logging%20is%20currently%20not%3CBR%20%2F%3Esupported%20in%20offline%20servicing%20scenarios.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStep%20-%20DISM%20%2FOnline%20%2FCleanup-Image%20%2FRestoreHealth%3C%2FP%3E%3CP%3EResult%20-%26nbsp%3B%3C%2FP%3E%3CP%3EDeployment%20Image%20Servicing%20and%20Management%20tool%3CBR%20%2F%3EVersion%3A%2010.0.14393.4169%3C%2FP%3E%3CP%3EImage%20Version%3A%2010.0.14393.4169%3C%2FP%3E%3CP%3E%5B%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D100.0%25%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%5D%3CBR%20%2F%3EError%3A%200x800f081f%3C%2FP%3E%3CP%3EThe%20source%20files%20could%20not%20be%20found.%3C%2FP%3E%3CP%3E**%3CSTRONG%3ENOTE%3A%26nbsp%3B%3C%2FSTRONG%3EI%20have%20tried%20using%20a%20known%20good%20server%2C%20live%20and%20running%2C%20as%20a%20source.%20I%20have%20also%20tried%20using%20the%20install%20ISO%20as%20a%20source.**%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStep%20-%26nbsp%3B%3CSPAN%3EDISM%20%2FOnline%20%2FCleanup-Image%20%2FStartComponentCleanup%20%2FResetBase%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EResult%20-%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EDeployment%20Image%20Servicing%20and%20Management%20tool%3CBR%20%2F%3EVersion%3A%2010.0.14393.4169%3C%2FP%3E%3CP%3EImage%20Version%3A%2010.0.14393.4169%3C%2FP%3E%3CP%3E%5B%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D100.0%25%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%5D%3CBR%20%2F%3E%5B%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D100.0%25%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%5D%3CBR%20%2F%3EThe%20operation%20completed%20successfully.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20one%20time%20I%20enjoyed%20any%20success%20was%20last%20week.%20I%20decided%20to%20uninstall%20the%20most%20recent%20security%20updates.%20After%20doing%20so%20and%20rebooting%20the%20server%20I%20was%20able%20to%20install%20the%20MXDW%20and%20QuickBooks%20was%20able%20to%20generate%20PDFs!%20Yay!%20The%20following%20week%2C%20without%20installing%20any%20updates%20whatsoever%2C%20the%20problem%20returned.%20Now%20I%20am%20stuck.%20I%20have%20run%20Windows%20Update%20again%20and%20installed%20the%20latest%20patches.%20No%20joy.%20I%20have%20uninstalled%20those%20patches.%20No%20joy.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2647133%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2648295%22%20slang%3D%22en-US%22%3ERe%3A%20XPS%20Document%20Writer%20fails%20on%20Server%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2648295%22%20slang%3D%22en-US%22%3EDo%20you%20have%20access%20to%20Windows%2010%20device%3F%3CBR%20%2F%3EIf%20yes%2C%20open%20start%20and%20search%20for%20feedback%20and%20open%20Feedback%20Hub%20app%20and%20report%20this%20issue%20and%20attach%20these%20files%20there.%20In%20the%20list%2C%20select%20Windows%20Server.%3C%2FLINGO-BODY%3E
New Contributor

I have a copy of Windows Server 2016 running as a VM on a Dell PowerEdge with VMWare. This server is set up to be an application server, hosting QuickBooks Enterprise 2021.

 

A few weeks ago QuickBooks was suddenly unable to generate PDFs. After troubleshooting the cause it turns out that the XPS Document Writer had disappeared. The driver for the MXDW is still installed in the system. I cannot get the server to actually install a printer using that driver, which QuickBooks needs to generate PDFs. 

 

When attempting to install the printer manually with the Add Printer Wizard:

>Add a local printer with manual settings

>Use an existing port - PORTPROMPT: (Local Port)

>Select driver "Microsoft XPS Document Writer v4"

**NOTE: Have done this from Windows Update, and also selecting the actual driver from the driver store by selecting "have disk"**

>Two different errors are generated depending on what is selected next:

>>Use the driver that is currently installed - ERROR "Unable to install printer. The handle is invalid"

>>Replace the current driver - ERROR "Printer driver was not installed. Element not found."

 

When attempting to install the printer through the Print Management interface:

>Right click "Printers" under SERVER, select "Add Printer"

>Add a new printer using an existing port: PORTPROMPT: (Local Port)

>Use an existing printer driver on the computer - select from dropdown menu - "Microsoft XPS Document Writer v4"

>Printer Name - "Microsoft XPS Document Writer v4"

>ERROR - Unable to install printer. The handle is invalid.

 

Steps tried:

Step - sfc /scannow

Result - 

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

 

Step - DISM /Online /Cleanup-Image /RestoreHealth

Result - 

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.

**NOTE: I have tried using a known good server, live and running, as a source. I have also tried using the install ISO as a source.**

 

Step - DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Result - 

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================100.0%==========================]
[==========================100.0%==========================]
The operation completed successfully.

 

The one time I enjoyed any success was last week. I decided to uninstall the most recent security updates. After doing so and rebooting the server I was able to install the MXDW and QuickBooks was able to generate PDFs! Yay! The following week, without installing any updates whatsoever, the problem returned. Now I am stuck. I have run Windows Update again and installed the latest patches. No joy. I have uninstalled those patches. No joy.

1 Reply
Do you have access to Windows 10 device?
If yes, open start and search for feedback and open Feedback Hub app and report this issue and attach these files there. In the list, select Windows Server.