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.