- Remove From My Forums
-
Question
-
Hello,
on a lot of clients in my environment I have the following failure during CCMSetup:
What I already tried was the following:
cmd with elevated rightsbitsadmin /reset /allusers sc config winmgmt start= disabled net stop winmgmt Winmgmt /salvagerepository %windir%System32wbem sc config winmgmt start= auto shutdown /r /t 00 ccmsetup.exe
whereas it tells me the WMI is all okay
Thank you for help in advance.
kind regards
MK-Maddin
Here again the full ccmsetup.log
==========[ ccmsetup started in process 1016 ]========== ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Running on platform X64 ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Launch from folder C:Windowsccmsetup ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) CcmSetup version: 5.0.7804.1300 ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Running on OS (6.1.7600). Service Pack (0.0). SuiteMask = 256. Product Type = 1 ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Ccmsetup command line: ccmsetup.exe ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Local Machine is joined to an AD domain ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Current AD forest name is TEST.DOM, domain name is TEST.DOM ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Domain joined client is in Intranet ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) DhcpGetOriginalSubnetMask entry point is supported. ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Begin checking Alternate Network Configuration ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Failed to open to WMI namespace '\.rootccmNetworkConfig' (80041001) ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Finished checking Alternate Network Configuration ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Adapter {A9E3A706-3334-4B30-9352-B07C4094ED50} is DHCP enabled. Checking quarantine status. ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Current AD site of machine is Iphofen ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Attempting to query AD for assigned site code ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Performing AD query: '(&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=180945326)(MSSMSRangedIPHigh>=180945326))))' ccmsetup 11/14/2013 9:13:46 AM 4804 (0x12C4) Performing AD query: '(&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=10.201.0.0)(mSSMSRoamingBoundaries=Iphofen)(mSSMSSiteCode=KN1)))' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) LSIsSiteCompatible : Verifying Site Compatibility for <KN1> ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Current AD forest name is TEST.DOM, domain name is TEST.DOM ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Domain joined client is in Intranet ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) LSGetSiteVersionFromAD : Attempting to query AD for MPs for site 'KN1' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSSiteCode=KN1))' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) LSGetSiteVersionFromAD : Successfully retrieved version '5.00.7804.1300' for site 'KN1' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) LSIsSiteCompatible : Site Version = '5.00.7804.1300' Site Capabilities = <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities> ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) LSIsSiteVersionCompatible : Site Version '5.00.7804.1300' is compatible. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) LSIsSiteCompatible : Site <KN1> Version '5.00.7804.1300' is compatible. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) LSGetAssignedSiteFromAD : Trying to Assign to the Site <KN1> ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Got site code 'KN1' from AD. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=KN1))' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) OperationalXml '<ClientOperationalSettings><Version>5.00.7804.1300</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA00302010202101C75FD95D572BEBE46DB1DE208110525300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3132303830323037353433365A180F32313132303731303037353433365A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100AD97389299AB898CD95614D161A4DE0B48355B2177BC85BAF96464CB880A3800D215BFF4C9720FEBEC014DB08406E65406EE3F81DE70831A2C04D132707F2F98983A55341EF90FA4A89903B1F8ADBA085DE15DA10BB9DBEC2ECA3D7D7CF7F5282C7DB8B6065EDA46E575D4E977E36B6DC970D43CDE51BDFA40A63CA8443A1449083BE802AA46EE79BAC581E7849BF648F9A3F20F6EC3F6D2386A0BAB5754EAAFFA61AD51638F8587B767A48BFB048F0DA5BC52233BDCCE5DF58370E90093F8A1D4020FBBC1CB1667478D8B6C41ADD5EAD5B1852238FDF96666D9528BBF4F69FFCC070A4D994CCF8449AA3657DD07EB00B05C7FF160BC2FB049433F2EE5A044350203010001A33C303A30220603551D11041B3019821744452D4950482D5343434D30322E4B4E4155462E4C4F4330140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100192C530971EB93EDA640CB237C11267226BF383A62AE1A498C7C41D48F0F879BAC478542C03EE6493D226C714A87FE91BFE9FC9F43AB2F558A264BC00173908C501DB37B8E9C1EBD801B50F19E9D30A9ABECC8B78A8E420B0F31C25D2E03DEADD6A02EAF6B4E7A5C45E85DBA0DB2578D28C9551DA9507CEEABD97ADF90B073257F3134A11E99B6B32FC98F11C0068B1B039EEA3B07192D108490D93D5CE9DB0AD594480E3283D349D1037297EB3E2BFB03411F6D72EC75CD1E60F2E2BCA0BC0DCDDEE9B19944EAD2AC4C0F2D13332832F64EE753D057CB1E94DE2EB14387B7195FD4E5AC9F1EDF57230D46D6D728FD4BDF2D306743C1CEC015EF028B58469E00</SiteSigningCert></SecurityConfiguration><RootSiteCode>KN1</RootSiteCode><CCM> <CommandLine>SMSSITECODE=KN1 SMSCACHESIZE=5120 FSP=SCCM02.knauf.loc SMSMP=SCCM02.knauf.loc</CommandLine> </CCM><FSP> <FSPServer>SCCM02.TEST.DOM</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain Value="TEST.DOM" /><Forest Value="TEST.DOM" /></ClientOperationalSettings>' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Unable to open Registry key SoftwareMicrosoftCCM. Return Code [80070002]. Client HTTPS state is Unknown. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) The MP name retrieved is 'SCCM02.TEST.DOM' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) MP 'SCCM02.TEST.DOM' is compatible ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Retrieved 1 MP records from AD for site 'KN1' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) FromAD: FSP = SCCM02.TEST.DOM ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) FromAD: command line = SMSSITECODE=KN1 SMSCACHESIZE=5120 FSP=SCCM02.knauf.loc SMSMP=SCCM02.knauf.loc ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Current AD forest name is TEST.DOM, domain name is TEST.DOM ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Domain joined client is in Intranet ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Found MP http://SCCM02.TEST.DOM from AD ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) SslState value: 224 ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Ccmsetup was run without any user parameters specified. Running without registering ccmsetup as a service. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Detected sitecode 'KN1' from AD. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) CCMHTTPPORT: 80 ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) CCMHTTPSPORT: 443 ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) CCMHTTPSSTATE: 224 ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) CCMHTTPSCERTNAME: ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Lookup MP: SCCM02.TEST.DOM ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) FSP: SCCM02.TEST.DOM ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) CCMFIRSTCERT: 1 ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Config file: ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Retry time: 10 minute(s) ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) MSI log file: C:WindowsccmsetupLogsclient.msi.log ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) MSI properties: SMSSITECODE="KN1" SMSCACHESIZE="5120" FSP="SCCM02.TEST.DOM" SMSMP="SCCM02.TEST.DOM" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" SMSSLP="SCCM02.TEST.DOM" CCMFIRSTCERT="1" ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Source List: ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) MPs: ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) http://SCCM02.TEST.DOM ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Failed to open to WMI namespace '\.rootccm' (80041001) ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) No version of the client is currently detected. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Updated security on object C:Windowsccmsetup. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Sending Fallback Status Point message to 'SCCM02.TEST.DOM', STATEID='100'. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Failed to open to WMI namespace '\.rootccm' (80041001) ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Failed to get client version for sending messages to FSP. Error 0x80041001 ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Params to send FSP message '5.0.7804.1300 Deployment ' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Failed to open to WMI namespace '\.rootccm' (80041001) FSPStateMessage 11/14/2013 9:13:47 AM 4804 (0x12C4) State message with TopicType 800 and TopicId {8C9C5F8E-8425-4F32-AF55-381518FED7C7} has been sent to the FSP FSPStateMessage 11/14/2013 9:13:47 AM 4804 (0x12C4) Running as user "AdministrativeUser" ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Detected 28621 MB free disk space on system drive. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Checking Write Filter Status. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) SiteCode: KN1 ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) SiteVersion: 5.00.7804.1300 ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Only one MP http://SCCM02.TEST.DOM is specified. Use it. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Searching for DP locations from MP(s)... ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Current AD site of machine is Iphofen LocationServices 11/14/2013 9:13:47 AM 4804 (0x12C4) DHCP entry points already initialized. LocationServices 11/14/2013 9:13:47 AM 4804 (0x12C4) Begin checking Alternate Network Configuration LocationServices 11/14/2013 9:13:47 AM 4804 (0x12C4) Failed to open to WMI namespace '\.rootccmNetworkConfig' (80041001) LocationServices 11/14/2013 9:13:47 AM 4804 (0x12C4) Finished checking Alternate Network Configuration LocationServices 11/14/2013 9:13:47 AM 4804 (0x12C4) Adapter {A9E3A706-3334-4B30-9352-B07C4094ED50} is DHCP enabled. Checking quarantine status. LocationServices 11/14/2013 9:13:47 AM 4804 (0x12C4) Sending message body '<ContentLocationRequest SchemaVersion="1.00"> <AssignedSite SiteCode="KN1"/> <ClientPackage/> <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseInternetDP="0"> <ADSite Name="Iphofen"/> <Forest Name="TEST.DOM"/> <Domain Name="TEST.DOM"/> <IPAddresses> <IPAddress SubnetAddress="10.201.0.0" Address="10.201.1.174"/> </IPAddresses> </ClientLocationInfo> </ContentLocationRequest> ' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Sending message header '<Msg SchemaVersion="1.1"><ID>{79D9A7A5-05A8-4761-BF4C-D34F28F8A3CB}</ID><SourceHost>KG-5290</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:KG-5290:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>http://SCCM02.TEST.DOM</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2013-11-14T08:13:47Z</SentTime><Body Type="ByteRange" Offset="0" Length="1080"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) CCM_POST 'http://SCCM02.TEST.DOM/ccm_system/request' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Content boundary is '--aAbBcCdDv1234567890VxXyYzZ' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Received header '<Msg SchemaVersion="1.1"> <ID>{F2CD67E8-82D4-4291-98B7-07A75D988FC2}</ID> <SourceID>GUID:EB8B85ED-250B-4520-9101-06C93430A992</SourceID> <SourceHost>SCCM02</SourceHost> <TargetAddress>direct:KG-5290:LS_ReplyLocations</TargetAddress> <ReplyTo>MP_LocationManager</ReplyTo> <CorrelationID>{00000000-0000-0000-0000-000000000000}</CorrelationID> <Priority>3</Priority> <Timeout>600</Timeout> <TargetHost>KG-5290</TargetHost><TargetEndpoint>LS_ReplyLocations</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2013-11-14T08:13:47Z</SentTime><Body Type="ByteRange" Offset="0" Length="3606"/><Hooks><Hook3 Name="zlib-compress"/><Hook Name="authenticate"><Property Name="Signature">3082019506092A864886F70D010702A082018630820182020101310B300906052B0E03021A0500300B06092A864886F70D010701318201613082015D020101303A3026311630140603550403130D44452D4950482D5343434D3032310C300A06035504031303534D530210105AFCB3AF1AF2B9406751E41B1CD923300906052B0E03021A0500300D06092A864886F70D0101010500048201005E82E4EBC41D5FC8D34C9FB1AD60E5C6D52064BE25F50E6056D9AB6F987AADA0E37CB109EDA7BFE46EBD828EFF98C0105F1A23F90CBD2991A5D7D4E0C7C3C6BB7D9ED058490AFDBFB1F6A1CE5728AA12D8255774E3145986271BFDEEC25EB6EA660ADB3F2E8AB8A9A4490499A838ADD84C64E23A3722761EEADDF95D1E9DCA2C0D8F808A6CE0F380DB205565E935AAC8BF4543C9B75623882C6BD915BBD06686BDD67393FEFEBC83648A3F7486F566A1ED870CA131B15A1699F1BEFA585A7EDD909FFB1C100396CC2E3449F1C7B8D394BEF15F7C90147554E7C99DC47E63BB5A6817D109176ED8AD94DB11DCC32522E815F8C38CB5CCBCED33FAC18527B18FB6</Property><Property Name="AuthSenderMachine">SCCM02;SCCM02.TEST.DOM;</Property><Property Name="MPSiteCode">KN1</Property></Hook></Hooks><Payload Type="inline"/></Msg>' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Received reply body '<ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags="16777216"><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="KN1" MasterSiteCode="KN1" SiteLocality="LOCAL" IISPreferedPort="80" IISSSLPreferedPort="443"/><LocationRecords><LocationRecord><URL Name="http://SCCM02.TEST.DOM/SMS_DP_SMSPKG$/KN100002" Signature="http://SCCM02.TEST.DOM/SMS_DP_SMSSIG$/KN100002"/><ADSite Name="Iphofen"/><IPSubnets><IPSubnet Address="10.206.8.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>7804</Version><Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>SCCM02.TEST.DOM</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="1"/><Locality>LOCAL</Locality></LocationRecord><LocationRecord><URL Name="http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002" Signature="http://SCCM03.TEST.DOM/SMS_DP_SMSSIG$/KN100002"/><ADSite Name="Iphofen"/><IPSubnets><IPSubnet Address="10.206.8.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>7804</Version><Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>SCCM03.TEST.DOM</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="1"/><Locality>LOCAL</Locality></LocationRecord></LocationRecords></Site><Site><MPSite SiteCode="KN1" MasterSiteCode="KN1" SiteLocality="LOCAL"/><LocationRecords/></Site></Sites><ClientPackage FullPackageID="KN100002" FullPackageVersion="3" FullPackageHash="3275659F35C57548B0756367DBC0BB54DD3FDBDEB77C11F2725461CEFBF2D013" MinimumClientVersion="5.00.7804.1000" RandomizeMaxDays="1" ProgramEnabled="true" LastModifiedTime="30286814;3549965056" SiteVersionMatch="true" SiteVersion="5.00.7804.1000" EnablePeerCache="true"/></ContentLocationReply>' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Found local location 'http://SCCM02.TEST.DOM/SMS_DP_SMSPKG$/KN100002' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Found local location 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Discovered 2 local DP locations. ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) PROPFIND 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Got 401 challenge Retrying with Windows Auth... ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) PROPFIND 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Using DP location http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002 ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) GET 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002/ccmsetup.cab' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) Got 401 challenge Retrying with Windows Auth... ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) GET 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002/ccmsetup.cab' ccmsetup 11/14/2013 9:13:47 AM 4804 (0x12C4) C:Windowsccmsetupccmsetup.cab is Microsoft trusted. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Successfully extracted manifest file C:Windowsccmsetupccmsetup.xml from file C:Windowsccmsetupccmsetup.cab. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Retrieved client version '5.00.7804.1000' and minimum assignable site version '5.00.7783.1000' from manifest ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Checking compatibility of site version '5.00.7804.1300', expect newer than '5.00.7783.1000' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Site version '5.00.7804.1300' is compatible. Client deployment will continue. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Location 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002' passed site version check. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Loading manifest file: C:Windowsccmsetupccmsetup.xml ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Successfully loaded ccmsetup manifest file. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Checking if manifest version '5.00.7804.1000' is newer than the ccmsetup version '5.0.7804.1300' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Running from temp downloaded folder or manifest is not newer than ccmsetup. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'i386/vcredist_x86.exe' is applicable. Add to the list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'x64/vcredist_x64.exe' is applicable. Add to the list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'i386/vc50727_x86.exe' is not applicable. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'x64/vc50727_x64.exe' is applicable. Add to the list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'i386/WindowsUpdateAgent30-x86.exe' is not applicable. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'x64/WindowsUpdateAgent30-x64.exe' is applicable. Add to the list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'i386/msxml6.msi' is not applicable. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'x64/msxml6_x64.msi' is applicable. Add to the list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'i386/msrdcoob_x86.exe' is not applicable. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'x64/msrdcoob_amd64.exe' is not applicable. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'pkgmgr.exe' is not applicable. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'dism.exe' is applicable. Add to the list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'wimgapi.msi' is not applicable. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'i386/MicrosoftPolicyPlatformSetup.msi' is not applicable. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'x64/MicrosoftPolicyPlatformSetup.msi' is applicable. Add to the list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'i386/WindowsFirewallConfigurationProvider.msi' is not applicable. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'x64/WindowsFirewallConfigurationProvider.msi' is applicable. Add to the list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'i386/Silverlight.exe' is applicable. Add to the list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'i386/wic_x86_enu.exe' is not applicable. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'x64/wic_x64_enu.exe' is not applicable. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'i386/dotNetFx40_Client_x86_x64.exe' is applicable. Add to the list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'SCEPInstall.exe' is applicable. Add to the list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'i386/client.msi' is not applicable. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item 'x64/client.msi' is applicable. Add to the list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Default CSP Type is 24 ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Discovering whether item 'i386/vcredist_x86.exe' exists. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Detected item 'i386/vcredist_x86.exe' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Discovering whether item 'x64/vcredist_x64.exe' exists. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Detected item 'x64/vcredist_x64.exe' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Discovering whether item 'x64/vc50727_x64.exe' exists. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Upgrade code '{A8D19029-8E5C-4E22-8011-48070F9E796E}': product = '{071c9b48-7c32-4621-a0ac-3f809523288f}', installed = 1, version = 8.0.56336 ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Upgrade code '{A8D19029-8E5C-4E22-8011-48070F9E796E}': product = '{ad8a2fa1-06e7-4b0d-927d-6e54b3d31028}', installed = 1, version = 8.0.61000 ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Checking '{A8D19029-8E5C-4E22-8011-48070F9E796E}' version '8.0.61000' expecting >= '8.0.61000'. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Detected item 'x64/vc50727_x64.exe' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Discovering whether item 'x64/WindowsUpdateAgent30-x64.exe' exists. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Checking file 'C:Windowssystem32wuapi.dll' version '7.6.7600.0256' expecting >= '7.4.7600.226'. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Detected item 'x64/WindowsUpdateAgent30-x64.exe' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Discovering whether item 'x64/msxml6_x64.msi' exists. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Checking file 'C:Windowssystem32msxml6.dll' version '6.30.7600.17157' expecting >= '6.10.1129.0'. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Detected item 'x64/msxml6_x64.msi' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Discovering whether item 'dism.exe' exists. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) File 'C:Windowssystem32msrdc.dll' exists. Discovery passed ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Detected item 'dism.exe' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Discovering whether item 'x64/MicrosoftPolicyPlatformSetup.msi' exists. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Upgrade code '{19B9818B-7432-49E9-BC02-B126025EE235}': product = '{376CBB7C-A86E-400D-8702-ABA2EFDE35D7}', installed = 1, version = 1.2.3520.0 ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Checking '{19B9818B-7432-49E9-BC02-B126025EE235}' version '1.2.3520.0' expecting >= '1.2.3602.0'. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item x64/MicrosoftPolicyPlatformSetup.msi has not been installed yet. Put to pending install list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Discovering whether item 'x64/WindowsFirewallConfigurationProvider.msi' exists. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) File 'C:WindowsccmsetupWindowsFirewallConfigurationProvider.msi' does not exist. Discovery failed. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item x64/WindowsFirewallConfigurationProvider.msi has not been installed yet. Put to pending install list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Discovering whether item 'i386/Silverlight.exe' exists. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) 32-bit Hive selected ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Detected item 'i386/Silverlight.exe' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Discovering whether item 'i386/dotNetFx40_Client_x86_x64.exe' exists. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Detected item 'i386/dotNetFx40_Client_x86_x64.exe' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Discovering whether item 'SCEPInstall.exe' exists. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item SCEPInstall.exe has not been installed yet. Put to pending install list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Discovering whether item 'x64/client.msi' exists. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Item x64/client.msi has not been installed yet. Put to pending install list. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) PROPFIND 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Got 401 challenge Retrying with Windows Auth... ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) PROPFIND 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) No client patches are detected. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) PROPFIND 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Got 401 challenge Retrying with Windows Auth... ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) PROPFIND 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Detected 5 client language packs. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Searching for available transform ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) PROPFIND 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Got 401 challenge Retrying with Windows Auth... ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) PROPFIND 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Found transform x64/LanguagePack/CLP1031.mst. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) File 'C:WindowsccmsetupMicrosoftPolicyPlatformSetup.msi' doesn't exist. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) File 'C:WindowsccmsetupWindowsFirewallConfigurationProvider.msi' doesn't exist. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) File 'C:WindowsccmsetupSCEPInstall.exe' doesn't exist. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) File 'C:Windowsccmsetupclient.msi' doesn't exist. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Failed to download client files by BITS. Error 0x800704dd ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Sending Fallback Status Point message to 'SCCM02.TEST.DOM', STATEID='309'. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Failed to open to WMI namespace '\.rootccm' (80041001) ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Failed to get client version for sending messages to FSP. Error 0x80041001 ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Params to send FSP message '5.0.7804.1300 Deployment Error 0x800704dd. Path http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Failed to open to WMI namespace '\.rootccm' (80041001) FSPStateMessage 11/14/2013 9:14:27 AM 4804 (0x12C4) State message with TopicType 800 and TopicId {3E9FB612-5542-4866-8FB7-BB0F8BD5CA5A} has been sent to the FSP FSPStateMessage 11/14/2013 9:14:27 AM 4804 (0x12C4) Failed to download from DP 'http://SCCM03.TEST.DOM/SMS_DP_SMSPKG$/KN100002', error 0x800704dd. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) PROPFIND 'http://SCCM02.TEST.DOM/SMS_DP_SMSPKG$/KN100002' ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Using DP location http://SCCM02.TEST.DOM/SMS_DP_SMSPKG$/KN100002 ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Failed to download client files by BITS. Error 0x800704dd ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Failed to download from DP 'http://SCCM02.TEST.DOM/SMS_DP_SMSPKG$/KN100002', error 0x800704dd. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Enumerated all 2 local DP locations but none of them is good. Fallback to MP. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Using branch cache option. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Adding file 'http://SCCM02.TEST.DOM:80/CCM_Client/x64/MicrosoftPolicyPlatformSetup.msi' to BITS job, saving as 'C:WindowsccmsetupMicrosoftPolicyPlatformSetup.msi'. ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Failed to download client files by BITS. Error 0x800704dd ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) Deleted file C:Windowsccmsetupccmsetup.xml ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4) CcmSetup failed with error code 0x800704dd ccmsetup 11/14/2013 9:14:27 AM 4804 (0x12C4)
Answers
-
Error code 4dd (hex) = 1245 = «The operation being requested was not performed because the user has not logged
on to the network. The specified service does not exist.» This clearly implies some sort of account issue. Exactly how are you initiating the client agent setup?
Jason | http://blog.configmgrftw.com
-
Marked as answer by
Tuesday, November 19, 2013 6:34 PM
-
Marked as answer by
-
Thank you for your help.
I just thought that having the screenshot with red marked info whould be more nice.
In case it whould be great to be able to upload logfiles (or mark as spoiler or something like this — not always posting as ‘code’).To come back to my problem.
I resolbed it What I did was copied cmtrace.exe, «<SMSINSTALLPATH>hotfixKB2854009Clientx64configmgr2012ac-sp1-kb2854009-x64.msp» and the folder «<SMSINSTALLPATH>Client» to a new folder.
In this folder I created a bat with the following content:@echo off SET MYDIR=%~dp0 IF NOT EXIST "%windir%ccmsetuplogs" MKDIR "%windir%ccmsetuplogs" IF NOT EXIST %windir%ccmsetuplogsccmsetup.log ECHO "==========[ ccmsetup script started ]==========" > %windir%ccmsetuplogsccmsetup.log @ping -n 2 %computername%>nul start %MYDIR%cmtrace.exe %windir%ccmsetuplogsccmsetup.log DEL /F /S /Q %windir%ccmsetuplogsccmsetup.log GOTO CCMUninstall :CCMUninstall @ECHO Uninstalling client... "%MYDIR%Clientccmsetup.exe" /uninstall @ECHO Post uninstall cleanup... IF EXIST %windir%CCM RMDIR /S /Q %windir%CCM IF EXIST %windir%ccmcache RMDIR /S /Q %windir%ccmcache IF EXIST %windir%ccmsetup RMDIR /S /Q %windir%ccmsetup GOTO REPAIR_WMI :REPAIR_WMI @ECHO Repairing WMI... sc config winmgmt start= disabled net stop winmgmt /y %SYSTEMDRIVE% >nul cd %windir%system32wbem For /f %%s in ('dir /b *.dll') do regsvr32 /s %%s wmiprvse /regserver REM winmgmt /regserver net start winmgmt for /f %%s in ('dir /b *.mof *.mfl') do mofcomp %%s @ECHO Waiting for WMI repair to finish... @ping -n 90 %computername%>nul GOTO REINSTALL_CLIENT :REINSTALL_CLIENT @ECHO Reinstalling Client... taskkill /IM CMTrace>nul IF NOT EXIST "%windir%ccmsetuplogs" MKDIR "%windir%ccmsetuplogs" IF NOT EXIST %windir%ccmsetuplogsccmsetup.log ECHO "==========[ ccmsetup script started ]==========" > %windir%ccmsetuplogsccmsetup.log @ping -n 2 %computername%>nul start %MYDIR%cmtrace.exe %windir%ccmsetuplogsccmsetup.log DEL /F /S /Q %windir%ccmsetuplogsccmsetup.log "%MYDIR%Clientccmsetup.exe" SMSCACHESIZE=5120 FSP=Primary.mydom SMSMP=Primary.mydom pause REM @ECHO Upgrading Client... REM taskkill /IM CMTrace>nul REM IF NOT EXIST "%windir%ccmsetuplogs" MKDIR "%windir%ccmsetuplogs" REM IF NOT EXIST %windir%ccmsetuplogsccmsetup.log ECHO "==========[ ccmsetup script started ]==========" > %windir%ccmsetuplogsccmsetup.log REM @ping -n 2 %computername%>nul REM start %MYDIR%cmtrace.exe %windir%ccmsetuplogsccmsetup.log REM DEL /F /S /Q %windir%ccmsetuplogsccmsetup.log REM "%MYDIR%ClientUpgradeccmsetup.exe" SMSCACHESIZE=5120 FSP=DE-IPH-SCCM02.knauf.loc SMSMP=DE-IPH-SCCM02.knauf.loc REM pause @ECHO Updating Client... SET MSIFILE=configmgr2012ac-sp1-kb2854009-x64.msp SET PAKETNAME=I-SWD_ConfigMgrClient_5.00.7804.1300_MUI_X64 SET SWNAME=ConfigMgrClient SET SWVERSION=5.00.7804.1300 SET PAKETVERSION=1.0 SET STARTTIME=%TIME:~0,2%-%TIME:~3,2%-%TIME:~6,2% SET LogName=%STARTTIME%_%PAKETNAME%_%PAKETVERSION%.log taskkill /IM CMTrace>nul IF NOT EXIST "%windir%ccmsetuplogs" MKDIR "%windir%ccmsetuplogs" IF NOT EXIST "%windir%ccmsetuplogs%LogName%" ECHO "==========[ ccmsetup script started ]==========" > "%windir%ccmsetuplogs%LogName%" @ping -n 2 %computername%>nul start %MYDIR%cmtrace.exe "%windir%ccmsetuplogs%LogName%" DEL /F /S /Q "%windir%ccmsetuplogs%LogName%" msiexec /update "%MYDIR%%MSIFILE%" /qn /norestart /l*v "%windir%ccmsetuplogs%LogName%" pause GOTO END :END ExitI already run the WMI repair before. I think it did not work because I did not uninstall and REINSTALL the client ( I saw during installation some WMI classes are registered).
With this script all of my devices worked correctly.
Thank you for help to everyone.
EDIT:
What I enabled now is client health check.
I think this can be very useful in situations like this.http://myitforum.com/myitforumwp/2012/06/26/client-health-check-in-configmgr-2012in-actionpart-2/
-
Marked as answer by
MK-Maddin
Tuesday, November 19, 2013 6:35 PM -
Edited by
MK-Maddin
Wednesday, November 20, 2013 9:58 AM
additional helpfull info
-
Marked as answer by
-
It was failing for me with the same error when I was running psexec.exe -i -s «ccmexec….». Once I have removed interactive flag «-i», issue was resolved.
-
Marked as answer by
Jason Sandys [MSFT]MVP
Saturday, October 7, 2017 3:56 AM
-
Marked as answer by
Symptoms of error 0x800704dd during ccmsetup
Error 0x800704dd or 800704dd may occur when you’re trying to install the SCCM client, using ccmsetup.exe. I used cmtrace to examine the ccmsetup.log and found the following passage:
Failed to download client files by BITS. Error 0x800704dd
Failed to open to WMI namespace ‘\.rootccm’ (80041001)
Failed to get client version for sending messages to FSP. Error 0x80041001
Failed to download from DP. Error 0x800704dd
Ccmsetup failed with error code 0x800704dd
A push installation as well as a manual installation failed.
Solution to error Ccmsetup failed with error code 0x800704dd
As it appears, the problem had something to do with a corrupt WMI repository. To solve this, you need to uninstall the (remains of the) ccm client, and then repair WMI on the machine. I found this handy topic on Microsoft. At the end of the discussion, MK-Maddin gives away his script to automatically fix the issue. To make sure the script is preserved, here’s the relevant part you need to run. After you have run this script, try to re-install the SCCM client:
IF NOT EXIST "%windir%ccmsetuplogs" MKDIR "%windir%ccmsetuplogs"
@ECHO Uninstalling client...
C:Windowsccmsetupccmsetup.exe" /uninstall
@ECHO Post uninstall cleanup...
IF EXIST %windir%CCM RMDIR /S /Q %windir%CCM
IF EXIST %windir%ccmcache RMDIR /S /Q %windir%ccmcache
IF EXIST %windir%ccmsetup RMDIR /S /Q %windir%ccmsetup
GOTO REPAIR_WMI
:REPAIR_WMI
@ECHO Repairing WMI...
sc config winmgmt start= disabled
net stop winmgmt /y
%SYSTEMDRIVE% >nul
cd %windir%system32wbem
For /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
wmiprvse /regserver
REM winmgmt /regserver
net start winmgmt
for /f %%s in ('dir /b *.mof *.mfl') do mofcomp %%s
@ECHO Waiting for WMI repair to finish...
@ping -n 90 %computername%>nul
Hi Guys ,
I am back with a new blog . This blog is about the SCCM client installation .I experienced this issue when I saw new Windows 10 computers which I imaged not able to download the content . Even though the client is added into proper boundary and assigned to a Distribution point.
Hence I thought to remove the client and reinstall . Once I removed the client it will not install and fail with the following error :
- Failed to download from DP , error 0x800704dd. ccmsetup 2018/11/16 16:55:21 18184 (0x4708)
- Adding file ‘http://:80/CCM_Client/x64/WindowsFirewallConfigurationProvider.msi’ to BITS job, saving as ‘C:WINDOWSccmsetupWindowsFirewallConfigurationProvider.msi’. ccmsetup 2018/11/16 16:55:21 18184 (0x4708)
- Failed to download client files by BITS. Error 0x800704dd ccmsetup 2018/11/16 16:55:21 18184 (0x4708)
Now if you simply uninstall the client and reinstall it will not work. To fix the issue please follow the following steps in order:
Clear up the previous installation information:
- Open CMD and go to the location where CCMSetup.exe resides on the managed device then run CCMSetup.exe /uninstall command
- Stop the services from task manager:
- SMS Agent Host Service
- CCMSetup service
- Delete following folders:
- windowsccm
- windowsccmsetup
2. windowsccmcacheDelete following files:
- windowssmscfg.ini
- windowssms*.mif (if present)
3. Delete following registry keys:
- HKLMsoftwareMicrosoftccm
- HKLMsoftwareMicrosoftCCMSETUP
- HKLMsoftwareMicrosoftSMS
4. Remove the 2 SMS certificates in the local certificate store
- Run MMC.exe as administrator and launch the certificate panel to the local computer
- Expand Certificates > SMS and Delete both certificates
5.Delete WMI namespace from powershell:
- rootccm
- Get-WmiObject -query “SELECT * FROM __Namespace WHERE Name=’CCM’” -Namespace “root” | Remove-WmiObject
- rootcimv2sms
- Get-WmiObject -query “SELECT * FROM __Namespace WHERE Name=’sms’” -Namespace “rootcimv2” | Remove-WmiObject
- In Task Scheduler library, under “Microsoft” delete the “Configuration Manager” folder and any tasks within it.
- Restart the machine.
Reinstall the SCCM client manually:
- Please copy the the whole client installation files from the network share folder \<Site Server Name>SMS_<Site Code>Client to C:tempClient.
- Run the below command
CCMSetup.exe /source C:tempClient SMSSITECODE= ABC SMSMP=MPServer.ABC.com
-
Thread Starter
-
#3
Saw that article, but the client does not even get installed. There is no installation file what’s so ever.
-
#4
WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account domainSCCM-ClientPush 00000035
The device computer does not exist on the network. Giving up
Can you confirm if you can resolve the remote computer name from your ConfigMgr server ?. It looks like its either a DNS issue or firewall.
-
Thread Starter
-
#5
WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account domainSCCM-ClientPush 00000035
The device computer does not exist on the network. Giving upCan you confirm if you can resolve the remote computer name from your ConfigMgr server ?. It looks like its either a DNS issue or firewall.
Yes, I can ping from both ways.
-
Thread Starter
-
#6
Yes, I can ping from both ways.
And the odd thing is that there are 3 laptop I am building remotely in the same location, and one of them did get the client installed.
-
#7
And the odd thing is that there are 3 laptop I am building remotely in the same location, and one of them did get the client installed.
Could you confirm to us that «domainSCCM-ClientPush» is member of the local administrator group?
Check also if there is any firewall or AV on this device.
-
Thread Starter
-
#8
Could you confirm to us that «domainSCCM-ClientPush» is member of the local administrator group?
Check also if there is any firewall or AV on this device.
Yes it is as stated in my original post.
-
#9
Are you able to access from the site server into this computer using c$?
-
Thread Starter
-
#10
Are you able to access from the site server into this computer using c$?
Yes I can. I did a workaround where I copied all the files over needed for the installation and that worked.
-
#11
Ok perfect. If you need to diagnose more this issue, I share with you the Client push installation prerequisites to check:
- Client Push Installation
-
Thread Starter
-
#12
Ok perfect. If you need to diagnose more this issue, I share with you the Client push installation prerequisites to check:
- Client Push Installation
The Push works fine on builds/rebuilds in the office, it is those I have to do in remote locations.
-
#13
Certainly, it’s a network issue. You have to monitor the traffic from end-to-end using WireShark or others monitoring tools to know which traffic are blocked by your FW.
I am using an MDT integrated UDI task sequence to deploy an operating system (Win7 x64), install the SCCM client then install applications/packages.
After the OS .wim file is applied the SCCM Client package is downloaded to C:_SMSTaskSequenceOSDSP100017
The machine then reboots and goes back into the task sequence to install the client, but fails. The appropriate bit of ccmsetup.log is below and the full file is attached
No transform available for this locale. Installation will proceed with no transformation. ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
File ‘C:WINDOWSccmsetupvcredist_x86.exe’ doesn’t exist. ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
File ‘C:WINDOWSccmsetupvcredist_x64.exe’ doesn’t exist. ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
File ‘C:WINDOWSccmsetupvc50727_x64.exe’ doesn’t exist. ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
File ‘C:WINDOWSccmsetupMicrosoftPolicyPlatformSetup.msi’ doesn’t exist. ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
File ‘C:WINDOWSccmsetupWindowsFirewallConfigurationProvider.msi’ doesn’t exist. ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
File ‘C:WINDOWSccmsetupSilverlight.exe’ doesn’t exist. ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
Using branch cache option. ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
Failed to download client files by BITS. Error 0x800704dd ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
A Fallback Status Point has not been specified and no client was installed. Message with STATEID=’309′ will not be sent. ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
Failed to send status 309. Error (87D00215) ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
Enumerated all 1 local DP locations but none of them is good. Fallback to MP. ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
Using branch cache option. ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
Failed to download client files by BITS. Error 0x800704dd ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
Deleted file C:WINDOWSccmsetupccmsetup.xml ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
CcmSetup failed with error code 0x800704dd ccmsetup 12/08/2015 15:46:29 2148 (0x0864)
Despite copying the files locally to C:_SMSTaskSequenceOSDSP100017 it is looking for them in C:windowsccmsetup, when it doesnt find them it tries to download them via BITS. The SCCM server is serving these files up ok (if I stick the URL to the file in a browser it serves it up without needing authentication). From hitting F8 during the task sequence and running «bitsadmin /list /allusers /verbose» it shows the BITS jobs are there but in a suspended state. Running «bitsadmin /listfiles <ID of bits job>» it shows no files in any of the bits jobs. «bitsadmin /reset» won’t cancel the jobs as they are running under SYSTEM. Also tried stopping the bits service, deleting the BITS related files under C:ProgramDataMicrosoft and starting the service, which clears the jobs from BITS but when ccmsetup.exe is rerun the jobs are readded as suspended and the same thing happens.
I also tried pausing the TS, copying the client files from C:_SMSTaskSequenceOSDSP100017 to where it is expecting (C:Windowsccmsetup) then resuming. However even though client.msi is in C:Windowsccmsetup where it is looking for it, it still tries to grab it via BITS and fails
No transform available for this locale. Installation will proceed with no transformation. ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Validated file ‘C:WINDOWSccmsetupvcredist_x86.exe’ hash ‘BBC26ACA42CD311A0E1EA1356852F061D863AF047F1891AC9952AB7E7CB8E04F’ ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Validated file ‘C:WINDOWSccmsetupvcredist_x64.exe’ hash ‘E8F443960B2F4A588902C3ED1603B07E29366B35D6CD1F06BC2544345D270D72’ ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Validated file ‘C:WINDOWSccmsetupvc50727_x64.exe’ hash ‘0551A61C85B718E1FA015B0C3E3F4C4EEA0637055536C00E7969286B4FA663E0’ ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Validated file ‘C:WINDOWSccmsetupMicrosoftPolicyPlatformSetup.msi’ hash ‘8C42189693C3220017E8C93A79B989EE126ADF33EADBE229011404C123B7B897’ ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Validated file ‘C:WINDOWSccmsetupSilverlight.exe’ hash ‘AFA7A7081D30B00A4F57C32932BD6D84940BB43B3F5FEB0828FF988C80E2D485’ ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Using branch cache option. ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Failed to download client files by BITS. Error 0x800704dd ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
A Fallback Status Point has not been specified and no client was installed. Message with STATEID=’309′ will not be sent. ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Failed to send status 309. Error (87D00215) ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Enumerated all 1 local DP locations but none of them is good. Fallback to MP. ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Using branch cache option. ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Failed to download client files by BITS. Error 0x800704dd ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
Deleted file C:WINDOWSccmsetupccmsetup.xml ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
CcmSetup failed with error code 0x800704dd ccmsetup 13/08/2015 10:14:52 948 (0x03B4)
C:Windowsccmsetupclient.msi defintately exists locally (tried with both 32 and 64 bit files) but for some reason it still wants to go off and grab it from the SCCM server via BITS.
I’ve searched high and low over the internet and read all the suggestions but am stumped.
ccmsetup.log
Hello,
I am having an issue manually installing the SCCM Client on a handful of workstations.
I have it pushing out via GPO, as well as installing during my PXE task sequence.
The GPO worked for about 90% of the workstations in my environment, but it didn’t for a handful, so I decided to just go do it manually on those workstations.
It worked for me perfectly on the first one I tried. However, every one after that, it will not install.
Please see my attached log files to see if you can help me out. I get the same errors at the bottom of each one.
This is an excerpt from the bottom of the log:
<![LOG[Failed to download client files by BITS. Error 0x800704dd]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»3″ thread=»192″ file=»ccmsetup.cpp:6814″>
<![LOG[Failed to get client version for sending state messages. Error 0x8004100e]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»2″ thread=»192″ file=»state.cpp:171″>
<![LOG[Params to send ‘5.0.8412.1004 Deployment Error 0x800704dd. Path http://cbsCM01.cb.local/SMS_DP_SMSPKG$/CBS00002’]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»0″ thread=»192″ file=»state.cpp:208″>
<![LOG[A Fallback Status Point has not been specified and no client was installed. Message with STATEID=’309′ will not be sent.]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»1″ thread=»192″ file=»state.cpp:222″>
<![LOG[Failed to send status 309. Error (87D00215)]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»3″ thread=»192″ file=»state.cpp:235″>
<![LOG[Failed to download from DP ‘http://cbsCM01.cb.local/SMS_DP_SMSPKG$/CBS00002’, error 0x800704dd.]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»2″ thread=»192″ file=»ccmsetup.cpp:1388″>
<![LOG[Enumerated all 1 DP locations but none of them is good. Fallback to MP.]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»2″ thread=»192″ file=»ccmsetup.cpp:11481″>
<![LOG[Cost settings successfully set on ‘{E2CD69D0-4F42-4D47-BE77-0D7E1D24EF81}’.]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»0″ thread=»192″ file=»ccmutillib.cpp:5781″>
<![LOG[Using branch cache option.]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»1″ thread=»192″ file=»ccmsetup.cpp:6639″>
<![LOG[Adding file ‘HTTP://cbsCM01:80/CCM_Client/i386/vcredist_x86.exe’ to BITS job, saving as ‘C:Windowsccmsetupvcredist_x86.exe’.]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»1″ thread=»192″ file=»ccmsetup.cpp:6670″>
<![LOG[Failed to download client files by BITS. Error 0x800704dd]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»3″ thread=»192″ file=»ccmsetup.cpp:6814″>
<![LOG[Failed to connect to policy namespace. Error 0x8004100e]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»3″ thread=»192″ file=»localpolicy.cpp:367″>
<![LOG[Failed to revoke client upgrade local policy. Error 0x8004100e]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»3″ thread=»192″ file=»localpolicy.cpp:394″>
<![LOG[Deleted file C:Windowsccmsetupccmsetup.xml]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»1″ thread=»192″ file=»ccmsetup.cpp:9772″>
<![LOG[CcmSetup failed with error code 0x800704dd]LOG]!><time=»09:26:52.580+480″ date=»12-14-2016″ component=»ccmsetup» context=»» type=»1″ thread=»192″ file=»ccmsetup.cpp:10927″>
I worked with my network engineer, who tells me the workstations have full access to this server. I even tried putting a workstation on the same VLAN as the server, and still get the same error.
Timeline is:
0. The GPO for Client deployment worked for ~90% of the workstations in my environment.
-
I try to manually install the client on my own workstation. It works without a problem. (SUCCESS-ccmclient.log)
-
I try to manually install the client on another workstation where it is missing. I get the error as shown in the log below. (FAILED-ccmclient.log)
-
I try 3 other workstations that don’t have the client, they all give the same error as the ‘FAILED’ log
-
I move the workstation to the same VLAN as the SCCM server, and still get the same error
Any assistance would be greatly appreciated.
Success-ccmclient.log
FAILED-ccmclient.log
EDIT: If you don’t want to download dropbox files, I made the same post on windows-noob over here where they allow .txt attachments.
- Remove From My Forums
-
Question
-
Hi ,
To get rid of the elevation prompt for running my application at startup as a standard user.I have created a task through task scheduler which has to run my application with trigger as at logon( logon by any user i presume) .I have checked Run only when an user is logged on in the Generals tab and also checked Run with highest privileges.
when i log in as an administrator the task runs perfectly fine but when i log in as a standard user ,i dont see the task running and when i check the status in the task scheduler it shows status as Ready but also displays
The operation being requested was not performed because the user has not logged on to the network.The specified service does not exist(0x800704DD)
i have no clue which service does not exist ….. phew
I have my application installed in C drive Program files , i cannot relocate my application. I need to run this application as a standard user without providing the admin password and also without moving it from Program file.
I am using Vista Enterprise 32 bit OS.
please help.
Thanks,
Sumaiya
Answers
На чтение 8 мин. Просмотров 538 Опубликовано 03.09.2019
Хотя Windows 10 является бесплатным обновлением для всех пользователей Windows 7 и Windows 8, это не значит, что обновление всегда проходит гладко. Пользователь сообщил об ошибке 0x800704DD-0x90016 во время установки Windows 10, поэтому давайте посмотрим, сможем ли мы как-то это исправить.
Если при обновлении до Windows 10 с Windows 7 или Windows 8 вы получаете сообщение об ошибке 0x800704DD-0x90016, вам нужно следовать этому простому решению.
Содержание
- Что делать, если вы не можете установить Windows 10 из-за ошибки 0x800704DD-0x90016
- Решение 1 – Переключиться на учетную запись администратора
- Решение 2. Включите скрытую учетную запись администратора
- Решение 3 – Отключить/удалить антивирус
- Решение 4. Отключите ненужные USB-устройства.
- Решение 5 – Выполните Чистую загрузку
- Решение 6 – Отключиться от Интернета во время установки
- Решение 7 – Загрузите ISO с другого ПК
- Решение 8. Запустите средство устранения неполадок Центра обновления Windows
Что делать, если вы не можете установить Windows 10 из-за ошибки 0x800704DD-0x90016
Ошибка 0x800704DD-0x90016 может быть проблематичной, и это может помешать вам установить Windows 10. Говоря об этом сообщении об ошибке, вот некоторые распространенные проблемы, с которыми столкнулись пользователи:
- Ошибка средства создания Windows 10 Media 0x800704dd 0x90016 – эта ошибка обычно появляется, если вы не используете учетную запись администратора. Чтобы это исправить, просто переключитесь на учетную запись администратора и попробуйте снова запустить Media Creation Tool.
- 0x800704dd-0x90016 Ноутбук с Windows 10 – эта проблема также может появляться на вашем ноутбуке. Если вы столкнулись с этой проблемой, просто выполните чистую загрузку и отключите подключение к Интернету во время установки.
Решение 1 – Переключиться на учетную запись администратора
Если вам не удается установить Windows 10 из-за ошибки 0x800704DD-0x90016, возможно, проблема в отсутствии административных прав. Чтобы решить эту проблему, вам просто нужно войти в Windows, используя учетную запись администратора, и попытаться снова запустить установку.
Если у вас нет учетной записи администратора, вы можете создать ее, выполнив следующие действия:
- Откройте приложение «Настройки». Вы можете сделать это быстро с помощью сочетания клавиш Windows + I.
-
Когда откроется приложение «Настройки», перейдите в раздел «Учетные записи».
-
Выберите «Семья и другие люди» в меню слева. Теперь нажмите кнопку «Добавить кого-то еще к этому ПК» на правой панели.
-
Вас попросят ввести регистрационную информацию для нового пользователя. Выберите, у меня нет информации для входа этого человека.
-
Теперь выберите Добавить пользователя без учетной записи Microsoft.
-
Введите желаемое имя пользователя и нажмите Далее.
После создания новой учетной записи пользователя ее необходимо преобразовать в учетную запись администратора. Для этого выполните следующие действия:
- В настройках приложения перейдите в раздел «Аккаунты»> «Семья и другие люди».
-
Найдите новую учетную запись и выберите «Изменить тип учетной записи».
-
Установите тип учетной записи «Администратор» и нажмите «ОК».
После создания новой учетной записи администратора переключитесь на нее и попробуйте снова запустить установку.
- ЧИТАЙТЕ ТАКЖЕ: ИСПРАВЛЕНИЕ: программе установки Windows не удалось установить один или несколько критичных для загрузки драйверов
Решение 2. Включите скрытую учетную запись администратора
Как мы уже упоминали в нашем предыдущем решении, ошибка 0x800704DD-0x90016 может возникнуть, если у вас нет необходимых привилегий, но вы можете получить эти привилегии, просто используя учетную запись администратора.
Если вы не хотите создавать новую учетную запись пользователя, вы всегда можете включить скрытую учетную запись администратора и использовать ее для установки Windows 10. Во всех версиях Windows эта скрытая учетная запись доступна, и вы можете переключиться на нее, выполнив следующие действия:
-
Запустите командную строку от имени администратора. Самый простой способ сделать это – нажать клавишу Windows + X и выбрать в меню командную строку (Admin) или PowerShell (Admin).
-
Когда откроется командная строка, запустите команду net user administrator/active: yes, чтобы включить скрытую учетную запись.
После выполнения этой команды скрытая учетная запись администратора должна быть включена, и вы сможете получить к ней доступ. Получив доступ к новой учетной записи администратора, попробуйте установить Windows 10.
Если процесс успешен, вы можете отключить скрытую учетную запись администратора, запустив командную строку и выполнив команду net user administrator/active: no .
Этот метод довольно эффективен, особенно если вы не хотите создавать новую учетную запись пользователя, поэтому вы можете попробовать ее.
Связано: FIX: после обновления учетная запись администратора Windows 10 отсутствует
Решение 3 – Отключить/удалить антивирус
Наличие хорошего антивируса важно, но иногда ваш антивирус может мешать установке Windows 10 и вызывать ошибку 0x800704DD-0x90016.Ваш антивирус не позволит определенным приложениям изменять системные файлы, и это приведет к возникновению этой проблемы.
Чтобы решить эту проблему, рекомендуется отключить антивирус перед попыткой установки Windows 10. Если отключение антивируса не помогает, рекомендуется полностью удалить антивирус и попытаться снова запустить установку. Чтобы убедиться, что ваш антивирус полностью удален, загрузите специальный инструмент для удаления вашего антивируса и запустите его.
После удаления антивируса попробуйте установить Windows 10 еще раз, и ошибка 0x800704DD-0x90016 не должна появляться. Если вам удастся завершить процесс установки, вам следует рассмотреть возможность установки нового антивируса на свой компьютер.
Bitdefender предлагает лучшую защиту на рынке и полностью совместим с Windows 10, поэтому он никак не повлияет на вашу систему. Если вы ищете хороший и надежный антивирус, Bitdefender может быть именно тем, что вам нужно.
- Читайте также: лучшие антивирусные решения Windows 10 для установки в 2019 году
Решение 4. Отключите ненужные USB-устройства.
Если при попытке установить Windows 10 у вас возникла ошибка 0x800704DD-0x90016, возможно, проблема в ваших USB-устройствах. Некоторые USB-устройства, такие как внешние жесткие диски, устройства для чтения карт памяти и т. Д., Могут иногда мешать установке Windows 10.
Чтобы убедиться, что процесс установки проходит гладко, мы настоятельно рекомендуем вам отключить все USB-устройства, кроме клавиатуры и мыши и установочного носителя. После того, как вы отключите все USB-устройства, у вас не должно возникнуть проблем с ним.
Решение 5 – Выполните Чистую загрузку
Сторонние приложения могут иногда мешать установке Windows 10, и если вы продолжаете получать 0x800704DD-0x90016, возможно, вам следует попробовать отключить автозапуск приложений и служб. Это довольно просто сделать, и вы можете сделать это, выполнив следующие действия:
-
Нажмите клавиши Windows + R, введите msconfig и нажмите кнопку «ОК» или нажмите «Ввод».
-
Откроется окно конфигурации системы. Перейдите на вкладку «Услуги». Теперь вам нужно установить флажок «Скрыть все службы Microsoft» и нажать кнопку «Отключить все».
-
Теперь перейдите на вкладку «Автозагрузка» и нажмите «Открыть диспетчер задач».
-
Список всех приложений теперь появится. Теперь вам нужно отключить все автозагрузки приложений. Для этого щелкните правой кнопкой мыши первое приложение в списке и выберите «Отключить». Повторите это для всех записей в списке.
-
После отключения запуска приложений вернитесь в окно «Конфигурация системы». Теперь нажмите «Применить» и «ОК», чтобы сохранить изменения и перезагрузить компьютер.
После этого все запускаемые приложения будут отключены. Теперь попробуйте установить Windows 10 снова и проверьте, сохраняется ли проблема.
Решение 6 – Отключиться от Интернета во время установки
По словам пользователей, если вы пытаетесь установить Windows 10 с помощью файла ISO, обязательно отключитесь от Интернета. Чтобы быть в безопасности, отсоедините кабель Ethernet, а в некоторых случаях вам даже может понадобиться отсоединить беспроводной адаптер от ПК.
После этого попробуйте установить Windows 10 снова.
- ЧИТАЙТЕ ТАКЖЕ: как переустановить Windows 10
Решение 7 – Загрузите ISO с другого ПК
Иногда файл ISO, который вы используете для установки Windows 10, не годится, и это может вызвать ошибку 0x800704DD-0x90016. Это может быть проблемой, но несколько пользователей сообщили, что вы можете решить эту проблему, просто загрузив файл ISO на другой компьютер и используя этот ISO для установки Windows 10.
Это звучит как необычное решение, но пользователи утверждают, что оно работает, поэтому вы можете попробовать его.
Связанные : как исправить ошибки Windows 10 при монтировании файлов ISO
Решение 8. Запустите средство устранения неполадок Центра обновления Windows
Если вы продолжаете получать ошибку 0x800704DD-0x90016 при попытке установить Windows 10, вы можете решить эту проблему, просто запустив средство устранения неполадок Центра обновления Windows. В Windows имеется множество средств устранения неполадок, и они предназначены для автоматического сканирования вашей системы и устранения различных проблем. Для запуска средства устранения неполадок Центра обновления Windows вам просто нужно сделать следующее:
- Нажмите клавишу Windows + I, чтобы открыть приложение «Настройки».
-
Теперь перейдите в раздел «Обновление и безопасность».
-
Выберите «Устранение неполадок» в меню слева. Выберите Центр обновления Windows из списка и нажмите кнопку Запустить средство устранения неполадок.
Следуйте инструкциям на экране для устранения неполадок. После устранения неполадок попробуйте установить Windows 10 снова.
Мы надеемся, что наши решения оказались полезными и что вам удалось исправить ошибку 0x800704DD-0x90016 на вашем компьютере.
Примечание редактора . Это сообщение было первоначально опубликовано в январе 2016 года и с тех пор было полностью переработано и обновлено для обеспечения свежести, точности и полноты.
С момента официального релиза ОС Windows 10 прошло уже больше недели. Однако, многие из пользователей продолжают искать баги и тестировать потенциал новой ОС. На сегодняшний день были определены уже практически все баги и ошибки Windows 10. Однако, если вы все еще в раздумьях, устанавливать ли Windows 10 или уже пытались инсталлировать обновление, но столкнулись с ошибкой «0x800704DD-0x90016», то знайте – вы не одиноки в своей проблеме, а саму ошибку можно решить.
Большинство пользователей сталкивается с ошибкой Windows 10 «Something Happened» («Что-то произошло»). Это достаточно распространенная проблема, характерная для пользователей, которые загружают обновление на Windows 7 или Windows 8.1. Однако, ошибка 0x800704DD-0x90016 иногда следует за ошибкой «Something Happened», и это затрагивает многих, у кого установлена пиратская версия Windows.
Кроме того, пользователи, скачавшие Windows 10 при помощи Media Creation Tool от Microsoft, также пишут на форумах о точно такой же ошибке.
Есть ли действенное решение этой проблемы? На сегодняшний день не так много пользователей столкнулись с ошибкой, а те, кто все же столкнулись, не смогли найти верное решение на различных форумах. Тем не менее, некоторые советы по решению ошибки 0x800704DD-0x90016 крутятся вокруг прав администратора.
Решение 1. Пользователи, запускавшие Media Creation Tool утверждают, что открытие приложения с правами администратора позволяет исправить ошибку. Лучший способ исправления ошибки – убедиться, что ваш аккаунт пользователя в Windows 7 или Windows 8.1 имеет все права администратора. Просто переключитесь на учетную запись администратора, и проблема должна быть решена.
Решение 2. Разрешение доступа для Windows Update – еще одно возможное решение вашей проблемы. Пользователи, которые скачивают Windows 10 через Windows Update, могут предоставить все необходимые доступы через командную строку. Для тех, кто не понимает, или настороженное относится к подобным вариантам настройки – не переживайте. Все, что от вас требуется, это скопировать и вставить в командную строку следующее предложение: «wuaucllt.exe /updatenow» без кавычек.
Чтобы запустить командную строку, через меню пуск откройте «Выполнить» и введите туда команду «cmd» без кавычек. Открывать командную строку необходимо в качестве администратора (или обладая всеми правами администратора).
После того, как введете в CMD «wuaucllt.exe /updatenow», обновление Windows 10 должно нормально запуститься.
Решение 3. Некоторые пользователи утверждают, что ошибка может быть вызвана вмешательством в процесс установки других сервисов. Отключение антивируса во время загрузки и установки обновления может увеличить скорость этих процессов. Наряду с этим, рекомендуется отключить все устройства USB, кроме мыши конечно и клавиатуры. После этого, попробуйте провести «чистую» загрузку и заново начните скачивание апдейта. Если что-то пошло не так и вновь появилась ошибка, отсоедините все устройства и воспользуйтесь ISO-образом с Windows 10 для установки файлов напрямую.
Если ни один из предложенных вариантов не помог вам в решении вопроса, пожалуйста, оставьте комментарий ниже, указав это. Если какое-либо из трех решения вам помогло, мы также просим написать об этом в комментариях.