Author eryksun
Recipients bfbfbfb bfbfbf, eryksun, paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2019-08-10.13:09:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1565442582.59.0.696468291921.issue37756@roundup.psfhosted.org>
In-reply-to
Content
If we see 0x8XXX_XXXX, it's either an NTSTATUS [1] warning, which is unlikely, or and HRESULT [2] error, which is very likely. One of the more common facility codes for HRESULT is the Windows API, 0x007. If we see 0x8007XXXX, then XXXX is a Windows system error code [3]. In this case, 0x643 is ERROR_INSTALL_FAILURE (1603), which is not a very information error code by itself. 

We need to read the log file (or request additional logs) to figure out what failed. Steve Dower is the person to address this, since he has far more experience with the design and behavior of the installer. From what I can see on the surface, with my shallow knowledge, it failed to install core_JustForMe for some reason (probably there's more info in another log), and then failed to delete the cached package when rolling back, with the error 0x80070003 (ERROR_PATH_NOT_FOUND), which looks suspicious.

I'm reopening for now. Feel free to close it again if you disagree. I won't press the matter.

[1] https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/87fba13e-bf06-450e-83b1-9241dc81e781
[2] https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/0642cb2f-2075-4469-918c-4441e69c548a
[3] https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes
History
Date User Action Args
2019-08-10 13:09:42eryksunsetrecipients: + eryksun, terry.reedy, paul.moore, tim.golden, zach.ware, steve.dower, bfbfbfb bfbfbf
2019-08-10 13:09:42eryksunsetmessageid: <1565442582.59.0.696468291921.issue37756@roundup.psfhosted.org>
2019-08-10 13:09:42eryksunlinkissue37756 messages
2019-08-10 13:09:42eryksuncreate