Replies

Need help running winget install wingetcreate on a Server 2019 (yes, I know the workarounds to get the winget-cli installed, and it is working). But I get an error when running winget install wingetcreate:

InstallFlowReturnCodeBlockedByPolicy

I can’t figure out what policy would block winget since I have it installed on my other Server 2016 and Win11 machines.

I have a similar but slightly different issue with KB4516655. It shows as installed on my Server 2008 R2 SP1 server, but now I’m getting an 80070490 error. When examining the CBS.log file, the error appears to be the WUAgent (snippet below):

2019-10-29 13:35:49, Error CBS Failed to internally open package. [HRESULT = 0x80070002 – ERROR_FILE_NOT_FOUND]
2019-10-29 13:36:06, Info CBS Session: 30772863_1473444514 initialized by client WindowsUpdateAgent.
2019-10-29 13:36:06, Info CBS Read out cached package applicability for package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320, ApplicableState: 80, CurrentState:112
2019-10-29 13:36:06, Info CBS Session: 30772863_1473444515 initialized by client WindowsUpdateAgent.
2019-10-29 13:36:06, Info CBS Failed to open package file: \\?\C:\Windows\Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~en-US~7.6.7600.256.mum [HRESULT = 0x80070002 – ERROR_FILE_NOT_FOUND]
2019-10-29 13:36:06, Info CBS Failed to read in xml content [HRESULT = 0x80070002 – ERROR_FILE_NOT_FOUND]
2019-10-29 13:36:06, Error CBS Failed to parse package manifest: \\?\C:\Windows\Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~en-US~7.6.7600.256.mum [HRESULT = 0x80070002 – ERROR_FILE_NOT_FOUND]
2019-10-29 13:36:06, Error CBS Failed to resolve package ‘WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~en-US~7.6.7600.256’ [HRESULT = 0x80070490 – ERROR_NOT_FOUND]
2019-10-29 13:36:06, Info CBS Failed to resolve package [HRESULT = 0x80070490 – ERROR_NOT_FOUND]
2019-10-29 13:36:06, Info CBS Failed to populate children. [HRESULT = 0x80070490 – ERROR_NOT_FOUND]
2019-10-29 13:36:06, Info CBS Failed to initialize internal package for package: WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.320 [HRESULT = 0x80070490 – ERROR_NOT_FOUND]
2019-10-29 13:36:06, Info CBS Delay load failed for package: WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320 [HRESULT = 0x80070490 – ERROR_NOT_FOUND]
2019-10-29 13:36:06, Error CBS Delay Initialization Failed [HRESULT = 0x80070490 – ERROR_NOT_FOUND]

Any ideas?

Joe,

While the early stage (“building .Net files” or something like that) takes quite a while, the longest time is after all Exchange services are shut down and the update is applying. Update Rollup 26 took over 30 hours just in that latter phase (and of course the Exchange services are all disabled during that time).

I have always disabled Avast for Business on the Exchange Server when applying the Update Rollups, but hadn’t heard about the IE setting. As soon as the April updates get an ok from the Master Patch List I’ll be trying Update 27 and so can try that IE setting change.

Sorry for the incomplete description. Answers to the questions by Joe and jabeattyauditor:

1. The server is running 2008R2 SP1. It is fully up-to-date through the March updates (holding off on April’s until all of the antivirus issues are resolved).

2. Exchange Server 2010 SP3, patched through Update Rollup 26 (that’s the one that took nearly 48 hours).

3. Disks are 15K 12GB/s SAS in a Raid 5 array.

4. We only have about 25 mailboxes with 4vCPUs and 16GB Ram. Could consider increasing both RAM and vCPUs.

Thanks for any help you can offer now.