0x80070002 net framework windows 10

27.02.2019, 17:41. Показов 12371. Ответов 2

добрый день.
при попытки установить .NET FRAMEWORK 3.5 через стандартный установщик компонентов

пишет «не удалось установить следующий компонент .NET FRAMEWORK 3.5
не удается найти указанный файл
код ошибки 0x80070002″

пересмотрел много способов установки но что то все четно.
пробовал
— через оффлайн установщик (выдает тоже самое)
— включал в компонентах виндовс
— в службах, центр обновления Windows запущен
— включал через редактор групповой политики (gpedit.msc)
— через PowerShell c флешки с дистрибутивом «Enable-WindowsOptionalFeature -Online -FeatureName «NetFx3» -Source

E:\sources\sxs» (выдает
«Enable-WindowsOptionalFeature : Не удается найти указанный файл.
строка:1 знак:1
+ Enable-WindowsOptionalFeature -Online -FeatureName «NetFx3» -Source E …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: ( [Enable-WindowsOptionalFeature], COMException
+ FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOpt ionalFeatureCommand»)

логи DISM

Кликните здесь для просмотра всего текста

2019-02-27 21:01:08, Info DISM DISM WIM Provider: PID=13004 TID=11548 [C:\] is not a WIM mount point. — CWimMountedImageInfo::Initialize
2019-02-27 21:01:08, Info DISM DISM VHD Provider: PID=13004 TID=11548 [C:\] is not recognized by the DISM VHD provider. — CVhdImage::Initialize
2019-02-27 21:01:08, Info DISM DISM FFU Provider: PID=13004 TID=11548 [C:\] is not recognized by the DISM FFU provider. — CFfuImage::Initialize
2019-02-27 21:01:08, Info DISM DISM Imaging Provider: PID=13004 TID=11548 The provider FfuManager does not support CreateDismImage on C:\ — CGenericImagingManager::CreateDismImage
2019-02-27 21:01:08, Info DISM DISM VHD Provider: PID=13004 TID=11548 [C:\] is not recognized by the DISM VHD provider. — CVhdImage::Initialize
2019-02-27 21:01:08, Info DISM DISM Imaging Provider: PID=13004 TID=11548 The provider VHDManager does not support CreateDismImage on C:\ — CGenericImagingManager::CreateDismImage
[13004] [0x8007007b] FIOReadFileIntoBuffer1381): Синтаксическая ошибка в имени файла, имени папки или метке тома.
[13004] [0xc142011c] UnmarshallImageHandleFromDirectory641)
[13004] [0xc142011c] WIMGetMountedImageHandle2897)
2019-02-27 21:01:08, Info DISM DISM WIM Provider: PID=13004 TID=11548 [C:\] is not a WIM mount point. — CWimMountedImageInfo::Initialize
2019-02-27 21:01:08, Info DISM DISM Imaging Provider: PID=13004 TID=11548 The provider WimManager does not support CreateDismImage on C:\ — CGenericImagingManager::CreateDismImage
2019-02-27 21:01:08, Info DISM DISM Imaging Provider: PID=13004 TID=11548 No imaging provider supported CreateDismImage for this path — CGenericImagingManager::CreateDismImage
2019-02-27 21:01:08, Info DISM DISM Manager: PID=13004 TID=11548 physical location path: C:\ — CDISMManager::CreateImageSession
2019-02-27 21:01:08, Info DISM DISM Manager: PID=13004 TID=11548 Event name for current DISM session is Global\{C2B5D8D4-A3B6-4412-BB25-99C79D950513} — CDISMManager::CheckSessionAndLock
2019-02-27 21:01:08, Info DISM DISM Manager: PID=13004 TID=11548 Create session event 0x884 for current DISM session and event name is Global\{C2B5D8D4-A3B6-4412-BB25-99C79D950513} — CDISMManager::CheckSessionAndLock
2019-02-27 21:01:08, Info DISM DISM Manager: PID=13004 TID=11548 Copying DISM from «C:\Windows\System32\Dism» — CDISMManager::CreateImageSessionFromLoca tion
2019-02-27 21:01:09, Info DISM DISM Manager: PID=13004 TID=11548 Successfully loaded the ImageSession at «C:\Users\Lex39\AppData\Local\Temp\F4871 1B7-506A-409A-9DBF-AF488D72C308» — CDISMManager::LoadRemoteImageSession
2019-02-27 21:01:09, Info DISM DISM Image Session: PID=13780 TID=5920 Instantiating the Provider Store. — CDISMImageSession::get_ProviderStore
2019-02-27 21:01:09, Info DISM DISM Provider Store: PID=13780 TID=5920 Initializing a provider store for the IMAGE session type. — CDISMProviderStore::Final_OnConnect
2019-02-27 21:01:09, Info DISM DISM Provider Store: PID=13780 TID=5920 Connecting to the provider located at C:\Users\Lex39\AppData\Local\Temp\F48711 B7-506A-409A-9DBF-AF488D72C308\OSProvider.dll. — CDISMProviderStore::Internal_LoadProvide r
2019-02-27 21:01:09, Info DISM DISM OS Provider: PID=13780 TID=5920 Defaulting SystemPath to C:\ — CDISMOSServiceManager::Final_OnConnect
2019-02-27 21:01:09, Info DISM DISM OS Provider: PID=13780 TID=5920 Defaulting Windows folder to C:\Windows — CDISMOSServiceManager::Final_OnConnect
2019-02-27 21:01:09, Info DISM DISM OS Provider: PID=13780 TID=5920 Host OS verion is 10.0 — CDISMOSServiceManager::SetDllSearchPath
2019-02-27 21:01:09, Warning DISM DISM OS Provider: PID=13780 TID=5920 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. — CDISMOSServiceManager::Final_OnConnect
2019-02-27 21:01:09, Info DISM DISM Provider Store: PID=13780 TID=5920 Attempting to initialize the logger from the Image Session. — CDISMProviderStore::Final_OnConnect
2019-02-27 21:01:09, Info DISM DISM Provider Store: PID=13780 TID=5920 Connecting to the provider located at C:\Users\Lex39\AppData\Local\Temp\F48711 B7-506A-409A-9DBF-AF488D72C308\LogProvider.dll. — CDISMProviderStore::Internal_LoadProvide r
2019-02-27 21:01:09, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-02-27 21:01:09, Info DISM DISM Provider Store: PID=13780 TID=5920 Found and Initialized the DISM Logger. — CDISMProviderStore::Internal_InitializeL ogger
2019-02-27 21:01:09, Warning DISM DISM Provider Store: PID=13780 TID=5920 Failed to load the provider: C:\Users\Lex39\AppData\Local\Temp\F48711 B7-506A-409A-9DBF-AF488D72C308\PEProvider.dll. — CDISMProviderStore::Internal_GetProvider (hr:0x8007007e)
2019-02-27 21:01:09, Info DISM DISM Provider Store: PID=13780 TID=5920 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. — CDISMProviderStore::Final_OnConnect
2019-02-27 21:01:09, Info DISM DISM Provider Store: PID=13780 TID=5920 Finished initializing the Provider Map. — CDISMProviderStore::Final_OnConnect
2019-02-27 21:01:09, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-02-27 21:01:09, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-02-27 21:01:09, Info DISM DISM Manager: PID=13004 TID=11548 Image session successfully loaded from the temporary location: C:\Users\Lex39\AppData\Local\Temp\F48711 B7-506A-409A-9DBF-AF488D72C308 — CDISMManager::CreateImageSession
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11548 Target image information: OS Version=10.0.17134.590, Image architecture=amd64 — CDismCore::LogImageSessionDetails
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Leave DismOpenSessionInternal — DismOpenSessionInternal
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Session id is: 2 — DismOpenSessionInternal
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Enter DismGetOsInfoInternal — DismGetOsInfoInternal
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Input parameters: Session: 2 — DismGetOsInfoInternal
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Initialized default cancel event — DismGetOsInfoInternal
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Successfully enqueued command object — CCommandThread::EnqueueCommandObject
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11548 ExecuteLoop: CommandQueue signaled — CCommandThread::ExecuteLoop
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11548 Successfully dequeued command object — CCommandThread:equeueCommandObject
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Leave DismGetOsInfoInternal — DismGetOsInfoInternal
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Enter DismDeleteInternal — DismDeleteInternal
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Leave DismDeleteInternal — DismDeleteInternal
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Enter DismEnableFeatureInternal — DismEnableFeatureInternal
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Enter DismEnableDisableFeatureInternal — DismEnableDisableFeatureInternal
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Input parameters: Session: 2, EnableFeatureName: NetFx3, DisableFeatureName: (null), Identifier: (null), PackageIdentifier: 0, LimitAccess: 0, SourcePathCount: 1, EnableAll: 0, CancelEvent: 0x0000000000000BEC, Progress: 0x000001B81BCF779C, UserData: 0x0000000000000000 — DismEnableDisableFeatureInternal
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Source path 0: E:\sources\sxs — DismEnableDisableFeatureInternal
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11112 Successfully enqueued command object — CCommandThread::EnqueueCommandObject
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11548 ExecuteLoop: CommandQueue signaled — CCommandThread::ExecuteLoop
2019-02-27 21:01:09, Info DISM API: PID=13004 TID=11548 Successfully dequeued command object — CCommandThread:equeueCommandObject
2019-02-27 21:01:09, Info DISM DISM Provider Store: PID=13780 TID=12664 Connecting to the provider located at C:\Users\Lex39\AppData\Local\Temp\F48711 B7-506A-409A-9DBF-AF488D72C308\CbsProvider.dll. — CDISMProviderStore::Internal_LoadProvide r
2019-02-27 21:01:09, Info DISM DISM Provider Store: PID=13780 TID=12664 Encountered a servicing provider, performing additional servicing initializations. — CDISMProviderStore::Internal_LoadProvide r
2019-02-27 21:01:09, Info CSI 00000001 Shim considered [l:125]’\??\C:\WINDOWS\Servicing\amd64_microsof t-windows-servicingstack_31bf3856ad364e35_10.0.171 34.580_none_ead976921d8220dc\wcp.dll’ : got STATUS_OBJECT_PATH_NOT_FOUND
2019-02-27 21:01:09, Info CSI 00000002 Shim considered [l:122]’\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.171 34.580_none_ead976921d8220dc\wcp.dll’ : got STATUS_SUCCESS
2019-02-27 21:01:12, Info DISM DISM Package Manager: PID=13780 TID=12664 Finished initializing the CbsConUI Handler. — CCbsConUIHandler::Initialize
2019-02-27 21:01:12, Info CSI 00000001 Shim considered [l:125]’\??\C:\WINDOWS\Servicing\amd64_microsof t-windows-servicingstack_31bf3856ad364e35_10.0.171 34.580_none_ead976921d8220dc\wcp.dll’ : got STATUS_OBJECT_PATH_NOT_FOUND
2019-02-27 21:01:12, Info CSI 00000002 Shim considered [l:122]’\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.171 34.580_none_ead976921d8220dc\wcp.dll’ : got STATUS_SUCCESS
2019-02-27 21:01:12, Info DISM DISM Package Manager: PID=13780 TID=12664 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log — CDISMPackageManager::Initialize
2019-02-27 21:01:12, Info DISM DISM Package Manager: PID=13780 TID=12664 Loaded servicing stack for online use only. — CDISMPackageManager::CreateCbsSession
2019-02-27 21:01:12, Info DISM DISM Package Manager: PID=13780 TID=5920 Initiating Changes on Package with values: 5, 7 — CDISMPackage::Internal_ChangePackageStat e
2019-02-27 21:01:12, Info DISM DISM Package Manager: PID=13780 TID=5920 CBS session options=0x40100! — CDISMPackageManager::Internal_Finalize
2019-02-27 21:01:40, Info DISM DISM Package Manager: PID=13780 TID=12664 Error in operation: (null) (CBS HRESULT=0x80070002) — CCbsConUIHandler::Error
2019-02-27 21:01:43, Error DISM DISM Package Manager: PID=13780 TID=5920 Failed finalizing changes. — CDISMPackageManager::Internal_Finalize(h r:0x80070002)
2019-02-27 21:01:43, Error DISM DISM Package Manager: PID=13780 TID=5920 Failed processing package changes with session options — CDISMPackageManager::ProcessChangesWithO ptions(hr:0x80070002)
2019-02-27 21:01:43, Error DISM API: PID=13004 TID=11548 Failed to process features change — CEnableDisableFeatureCommandObject::Inte rnalExecute(hr:0x80070002)
2019-02-27 21:02:30, Error DISM API: PID=13004 TID=11548 InternalExecute failed — CBaseCommandObject::Execute(hr:0x8007000 2)
2019-02-27 21:02:30, Error DISM API: PID=13004 TID=11112 CEnableDisableFeatureCommandObject internal execution failed — DismEnableDisableFeatureInternal(hr:0x80 070002)
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11112 Exit DismEnableDisableFeatureInternal — DismEnableDisableFeatureInternal
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11112 Exit DismEnableFeatureInternal — DismEnableFeatureInternal
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11112 Enter DismGetLastErrorMessageInternal — DismGetLastErrorMessageInternal
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11112 Exit DismGetLastErrorMessageInternal — DismGetLastErrorMessageInternal
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11112 Enter DismDeleteInternal — DismDeleteInternal
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11112 Leave DismDeleteInternal — DismDeleteInternal
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11112 Enter DismCloseSessionInternal — DismCloseSessionInternal
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11112 Input parameters: Session: 2 — DismCloseSessionInternal
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11112 GetReferenceCount hr: 0x0 — CSessionTable::RemoveSession
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11112 Refcount for DismSession= 2s 0 — CSessionTable::RemoveSession
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11112 Successfully enqueued command object — CCommandThread::EnqueueCommandObject
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11548 ExecuteLoop: CommandQueue signaled — CCommandThread::ExecuteLoop
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11548 Successfully dequeued command object — CCommandThread:equeueCommandObject
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11548 ExecuteLoop: Cancel signaled — CCommandThread::ExecuteLoop
2019-02-27 21:02:30, Info DISM API: PID=13004 TID=11548 Leave CCommandThread::ExecuteLoop — CCommandThread::ExecuteLoop
2019-02-27 21:02:30, Info DISM DISM Provider Store: PID=13780 TID=5920 Found the OSServices. Waiting to finalize it until all other providers are unloaded. — CDISMProviderStore::Final_OnDisconnect
2019-02-27 21:02:30, Info DISM DISM Provider Store: PID=13780 TID=5920 Found the OSServices. Waiting to finalize it until all other providers are unloaded. — CDISMProviderStore::Final_OnDisconnect
2019-02-27 21:02:30, Info DISM DISM Provider Store: PID=13780 TID=5920 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. — CDISMProviderStore::Final_OnDisconnect
2019-02-27 21:02:30, Info DISM DISM Provider Store: PID=13780 TID=5920 Finalizing the servicing provider(DISM Package Manager) — CDISMProviderStore::Internal_DisconnectP rovider
2019-02-27 21:02:30, Info DISM DISM Package Manager: PID=13780 TID=5920 Finalizing CBS core. — CDISMPackageManager::Finalize
2019-02-27 21:02:30, Info DISM DISM Provider Store: PID=13780 TID=5920 Disconnecting Provider: DISM Package Manager — CDISMProviderStore::Internal_DisconnectP rovider
2019-02-27 21:02:30, Info DISM DISM Provider Store: PID=13780 TID=5920 Releasing the local reference to OSServices. — CDISMProviderStore::Internal_DisconnectP rovider
2019-02-27 21:02:30, Info DISM DISM Provider Store: PID=13780 TID=5920 Disconnecting Provider: OSServices — CDISMProviderStore::Internal_DisconnectP rovider
2019-02-27 21:02:30, Info DISM DISM Provider Store: PID=13780 TID=5920 Releasing the local reference to DISMLogger. Stop logging. — CDISMProviderStore::Internal_DisconnectP rovider
2019-02-27 21:02:31, Info DISM DISM Manager: PID=13004 TID=11548 Closing session event handle 0x884 — CDISMManager::CleanupImageSessionEntry
2019-02-27 21:02:31, Info DISM DISM Provider Store: PID=13004 TID=11548 Found the OSServices. Waiting to finalize it until all other providers are unloaded. — CDISMProviderStore::Final_OnDisconnect
2019-02-27 21:02:31, Info DISM DISM Provider Store: PID=13004 TID=11548 Disconnecting Provider: FolderManager — CDISMProviderStore::Internal_DisconnectP rovider
2019-02-27 21:02:31, Info DISM DISM Provider Store: PID=13004 TID=11548 Disconnecting Provider: FfuManager — CDISMProviderStore::Internal_DisconnectP rovider
2019-02-27 21:02:31, Info DISM DISM Provider Store: PID=13004 TID=11548 Disconnecting Provider: WimManager — CDISMProviderStore::Internal_DisconnectP rovider
2019-02-27 21:02:31, Info DISM DISM Provider Store: PID=13004 TID=11548 Disconnecting Provider: VHDManager — CDISMProviderStore::Internal_DisconnectP rovider
2019-02-27 21:02:31, Info DISM DISM Provider Store: PID=13004 TID=11548 Disconnecting Provider: GenericImagingManager — CDISMProviderStore::Internal_DisconnectP rovider
2019-02-27 21:02:31, Info DISM DISM Provider Store: PID=13004 TID=11548 Disconnecting Provider: Compatibility Manager — CDISMProviderStore::Internal_DisconnectP rovider
2019-02-27 21:02:31, Info DISM DISM Provider Store: PID=13004 TID=11548 Releasing the local reference to DISMLogger. Stop logging. — CDISMProviderStore::Internal_DisconnectP rovider
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=11548 Leave CCommandThread::CommandThreadProcedureSt ub — CCommandThread::CommandThreadProcedureSt ub
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=11112 Leave DismCloseSessionInternal — DismCloseSessionInternal
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=11112 Enter DismShutdownInternal — DismShutdownInternal
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=11112 GetReferenceCount hr: 0x0 — CSessionTable::RemoveSession
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=11112 Refcount for DismSession= 1s 0 — CSessionTable::RemoveSession
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=4304 ExecuteLoop: CommandQueue signaled — CCommandThread::ExecuteLoop
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=11112 Successfully enqueued command object — CCommandThread::EnqueueCommandObject
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=4304 Successfully dequeued command object — CCommandThread:equeueCommandObject
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=4304 ExecuteLoop: Cancel signaled — CCommandThread::ExecuteLoop
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=4304 Leave CCommandThread::ExecuteLoop — CCommandThread::ExecuteLoop
2019-02-27 21:02:31, Info DISM PID=13004 TID=4304 Temporarily setting the scratch directory. This may be overridden by user later. — CDISMManager::FinalConstruct
2019-02-27 21:02:31, Info DISM PID=13004 TID=4304 Scratch directory set to ‘C:\Users\Lex39\AppData\Local\Temp\’. — CDISMManager:ut_ScratchDir
2019-02-27 21:02:31, Info DISM PID=13004 TID=4304 DismCore.dll version: 10.0.17134.1 — CDISMManager::FinalConstruct
2019-02-27 21:02:31, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=4304 Leave CCommandThread::CommandThreadProcedureSt ub — CCommandThread::CommandThreadProcedureSt ub
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=11112 Deleted g_internalDismSession — DismShutdownInternal
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=11112 Shutdown SessionTable — DismShutdownInternal
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=11112 Leave DismShutdownInternal — DismShutdownInternal
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=11112 DismApi.dll: — DismShutdownInternal
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=11112 DismApi.dll: <—— Ending DismApi.dll session ——> — DismShutdownInternal
2019-02-27 21:02:31, Info DISM API: PID=13004 TID=11112 DismApi.dll: — DismShutdownInternal

подскажите в какую сторону идти, куда копать, что делать?



0



Источник

Sysnative Forums

Картинка с сайта: www.sysnative.com

  • Microsoft Support & Malware Removal

  • Windows Update

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

Receiving error 0x80070002 when installing .NET 3.5

  • Thread starter
    Thread starter

    Vanir

  • Start date
    Start date

Joined
Mar 31, 2016
Posts
1




  • #1

So I’ve been attempting to install .NET 3.5 on Windows 10, and have been receiving the error 0x80070002 when using the installer provided here: Download Microsoft .NET Framework 3.5 from Official Microsoft Download Center

After some testing (manually enabling it via programs and features, running DISM directed towards the \sources\sxs folder on a mounted windows 10 ISO) I still can’t get it to install.

I’ve had some help from Tekno Venus, who’s had me run two SFCFix processes and a Collect.exe.

Still, it’s not working, and I was hoping you guys might be able to lend me a hand.

Below is the result of the first SFCFix:

PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs


Successfully created directory tree \\?\C:\Windows\winsxs\x86_system.data_b77a5c561934e089_10.0.10586.11_none_a34a50750a621afc.


Successfully copied file C:\Users\Vanir\AppData\Local\niemiro\Archive\x86_system.data_b77a5c561934e089_10.0.10586.11_none_a34a50750a621afc\System.Data.dll to C:\Windows\winsxs\x86_system.data_b77a5c561934e089_10.0.10586.11_none_a34a50750a621afc\System.Data.dll.


Successfully restored ownership for C:\Windows\winsxs
Successfully restored permissions on C:\Windows\winsxs
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2016-03-31 22:32:04.372
Script hash: A8NVXTRWpfLv1LVxRKUVvU/BNkGUozSLpc8HfORlI8U=
----------------------EOF-----------------------

Here is a link to my vslogs.zip generated by the collect.exe:
Dropbox — vslogs.zip

The SFCFix.txt attached is the most recent result.

Attachments


  • SFCFix.txt

Aura

Sysnative Staff, Security Analyst

Joined
Mar 16, 2015
Posts
8,061




  • #2

Hi Vanir :)

My name is Aura and I’ll be assisting you with your issue. On Windows 10, you don’t need to install .NET Framework 3.5. You can enable it directly from the Control Panel, under Programs and Features and «Turn Windows Features On or Off». In the list, you should see .NET Framework 3.5. Can you check if the box is checked, and if not, do it and see if it can be applied? If it doesn’t work from there, what error code are you getting?

Has Sysnative Forums helped you? Please consider donating to help us support the site!

  • Microsoft Support & Malware Removal

  • Windows Update

Источник

How to fix the issue reported by «error code net-framework-3.5-0x80070002»

Special Offer

Instructions

The following steps should fix the net-framework-3.5-0x80070002 issue:

  • Step 1.Download Outbyte PC Repair application See more information about Outbyte uninstall instructions EULA Privacy Policy
  • Step 2.Install and launch the application
  • Step 3.Click the Scan Now button to detect issues and abnormalities
  • Step 4.Click the Repair All button to fix the issues
Compatibility Win 11, 10, 8, 7
Download Size 21.2 MB
Requirements 300 MHz Processor, 256 MB RAM, 50 MB HDD

Limitations: trial version offers an unlimited number of scans, backups and restores of your Windows system elements for free. Registration for the full version starts from USD 29.95.

A malfunction reported by «error code net-framework-3.5-0x80070002» may happen due to a number of different factors. Common causes include incorrectly configured system settings or irregular entries in the system elements, to name a few. Such issues may be resolved with special software that repairs system elements and tunes system settings to restore stability.

The article provides details on what the issue means, potential causes, and ways to resolve the issue.

  • 1Meaning of the «error code net-framework-3.5-0x80070002»
  • 2Causes of the «error code net-framework-3.5-0x80070002»
  • 3Ways to repair the «error code net-framework-3.5-0x80070002»

Meaning of the «error code net-framework-3.5-0x80070002»

«Error code net-framework-3.5-0x80070002» is an issue name that usually contains details of the malfunction, including why it occurred, which system component or application malfunctioned, along with some other information. The numerical code in the issue name usually contains data that can be deciphered by the manufacturer of the component or application that malfunctioned. The issue with using this code may occur in many different locations within the system, so even though it carries some details in its name, it is still difficult for a user to pinpoint and fix the issue cause without specific technical knowledge or appropriate software.

Causes of the «error code net-framework-3.5-0x80070002»

If you have received this warning on your PC, it means that there was a malfunction in your system operation. «Error code net-framework-3.5-0x80070002» is one of the issues that users get as a result of the incorrect or failed installation or uninstallation of software that may have left invalid entries in your system elements, improper system shutdown due to a power failure or another factor, someone with little technical knowledge accidentally deleting a necessary system file or system element entry, as well as a number of other causes.

Ways to repair the «error code net-framework-3.5-0x80070002»

For an immediate fix of such issues, advanced PC users may be able to repair it by manually editing system elements, and others may want to hire a technician to do it for them. However, since any manipulations with Windows system elements carry a risk of rendering the operating system unbootable, whenever a user is in any doubt of their technical skills or knowledge, they should use a special type of software that is meant to repair Windows system elements without requiring any special skills from the user.

The following steps should help fix the issue:

  • Download Outbyte PC Repair application Special offer. See more information about Outbyte uninstall instructions EULA Privacy Policy
  • Install and launch the application
  • Click the Scan Now button to detect potential issue causes
  • Click the Repair All button to fix found abnormalities

The same application can be used to run preventative measures to reduce the chance of this or other system issues appearing in the future.

Источник

Failure of Windows 10/11 update shows Error Code 0x80070002, this article explains you the reasons for the failure of Windows 10/11 update. We have explained how the dependencies of system power network effects your updates. The main cause could be that system time is in error.

The interfaces in Windows 10 or 8.1 or 7 is different. But the possible solutions are common. Update components and services may not be working. Read below to find a solution for 0x80070002 error. The usual causes for this windows 11 update error code 0x80070002 are communication failure over the internet with Microsoft Windows update servers.

Error Code 0x80070002

Картинка с сайта: www.winchatsupport.com

How to Fix this Update Error 0x80070002 in Windows 10/11?

If you face Windows 10 upgrade error 0x80070002 in recent times, then it could be easily solved. This error code is related to Date and Time. Another way is to try the Windows Update Troubleshooter using the Settings app. 

How to Sync Date and Time for Windows 10 update Error code 0x80070002?

Make sure the CMOS battery is working perfectly and not dead. Otherwise, every time you restart your computer, the system time changes to default. In some cases, your local zone time and the system time are different. 

  • Firstly, right-click the date and time and click on “Adjust date/time”
  • It will open up Time & Language in the Settings app
  • On the left-hand side, you can see “Date & time”
  • On the right-hand side, make sure the following options are turned on 
    1. Set time automatically
    2. Set time zone automatically
  • For Region, select your correct country location   
  • After that, make sure the time server is one of the Windows 10 supported ones
  • Finally, Click on “Sync Now”

Error code 0x80070002

Картинка с сайта: www.winchatsupport.com

It will update the system time to the latest time of your time zone. Now restart and check. Time should be correct. If you are successful, then the error code 0x80070002 is resolved and can update to 20H2, the recent Windows 10 version. 

Try the Windows Update Troubleshooter to fix the Error Code 0x80070002 in Windows 10/11

It is a common step to check if you get any Windows Update Error 0x80070002. You can visit Settings > Update & Security and try the Update Troubleshooter app. It will also fix any update errors. 

Remove Third-Party Antivirus

If you are using any third-party virus in Windows 10, then you can remove them. Then try to rerun the Update tool.  You need not worry if you remove the third-party antivirus. Then after checking for updates, you can re-install it.  Always remember to keep only one antivirus on your system. If you are using more than one AV, then also it causes an issue.

NET Framework 3.5 0x80070002

In some cases, .NET may not be installed due to this update error. In such cases, you need to fix this first. Check whether .NET 3.5 is installed or not on your Windows 10 computer by using elevated PowerShell. 

  1. Firstly, search for “PowerShell” in the Windows 10 Search box
  2. Then right-click Windows Powershell and Run as Administrator

It will open Powershell in elevated command mode. Then run the following command. 

Get-WindowsOptionalFeature -Online -FeatureName netfx3

Error code 0x80070002

Картинка с сайта: www.winchatsupport.com

You will get the Status Enabled if it already exists. Any error, then follow these steps. 

  1. Download the Windows 10 ISO from Microsoft site
  2. If you already have the installation media files, then mount the disc or USB
  3. Identify the letter where the mounted ISO files are. It can be H: or F: or anything
  4. Now run the following command
Add-WindowsCapability -Online -Name NetFx3~~~~ -Source G:\Sources\SxS

Where G: is the drive letter where ISO files are mounted. It will install the NET 3.5 and wait for the process to complete. Then try the Windows Update again. 

.NET framework 3.5 error 0x80070002

You can download the repair tool from here. 

https://docs.microsoft.com/en-us/dotnet/framework/install/repair

It will repair the .NET files and install the required ones. You can try this for Windows 7 and 8.1 if you have the error 0x80070002. Then try the Update again. 

Perform a Clean Update

If you are facing error code 0x80070002 windows 10, then you can try the clean Upgrade. When you try to update to the 20H2 version from 1909 or any other older version, it can happen.  Run the Media Creation Tool from the above Windows 10 download link and select the option “Upgrade this PC now.” Select the option “Keep personal files and apps.” Then try to install.  It will update to the latest 20H2 Update. It is a manual process. 

Further Steps For Solving Error Code 0x80070002 in Windows 10/11

Disable the proxy internet connection and try again to install the update.

How to Disable the Proxy Connection in Windows for the Error Code 0x80070002?

  1. Firstly, open Internet Explorer and click on Tools->Internet Options
  2. Next, go to Connections and LAN Settings
  3. Finally, check to make sure the Proxy server is disabled.

Error Code 0x80070002 Solutions 

Second case would be with your Antivirus. There are proxy settings enabled under your settings of any security programs that you may be using. If you cannot find the procedure to stop it, you can ask our techs on chat support to guide you. Repair the Windows Update Services To Fix Error 0x80070002: There are failed windows update services that could also cause you this error 0x80070002 while updating Windows.

Try the below steps to repair Windows services

Repairing Windows update services is not possible like you repair any windows apps from the add/remove programs. There is a procedure that you need to follow through command lines. This requires the user to have administrator rights on his computer. As per the Microsoft set of rules defined on various Knowledge base articles, the steps are simplified as mentioned here to reset your windows update services.

NOTE: Following these steps carefully will not make any changes to your personal data or office programs. It will only reset the Windows update services.

Error Code Guide

  1. Firstly, open command prompt as administrator by right-clicking on it
  2. Then, go to c:\windows\ and rename software distribution folder to old
  3. In some cases it may not happen until you stop the windows update services
  4. To stop that, you can run a command-line net stop wuauserv and hit enter
    Error Code 0x8007000

    Картинка с сайта: www.winchatsupport.com

  5. After this,  you can try to rename this folder software distribution to old
  6. Then you can restart the windows update service
  7. After that, use this command “Net start wuauserv” and hit enter
    Error Code 0x8007000

    Картинка с сайта: www.winchatsupport.com

  8. Finally, check for updates now

Conclusion

If you still face issues related to windows update error 0x80070002, then it can be due to corrupted Windows Update component files. Also, some services may not be running, due to which this error crops up.

You can always chat with our Live Assist Team to resolve this error. It is more a quick solution to fix this error code 0x80070002.

Technical Support

Картинка с сайта: www.winchatsupport.com

Tags: Error 0x80070002, Error Code 0x80070002, Error Code 0x80070002 solutions, How to fix Error Code 0x80070002, Solutions for Error Code 0x80070002

Источник

Понравилась статья? Поделить с друзьями:
0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии
  • Xbox приложение для windows 10 для чего
  • Qt open source windows x86
  • Не запускается образ windows 10 с флешки
  • Множественное переименование файлов windows
  • Параметры конфиденциальности windows 10 при установке какие отключить лучше