Windows Server 2019 Cannot Install .NET 3.5
I am running Windows Server 2019 (Version 1809, Build 17763.4499) and I cannot install .NET Framework 3.5. Below is the current installation status of the feature on my machine: PS > Get-WindowsFeature -Name NET-Framework-Features,NET-Framework-Core,NET-HTTP-Activation,NET-Non-HTTP-Activ Display Name Name Install State ------------ ---- ------------- [X] .NET Framework 3.5 Features NET-Framework-Features Installed [ ] .NET Framework 3.5 (includes .NET 2.0 and 3.0) NET-Framework-Core Removed [ ] HTTP Activation NET-HTTP-Activation Removed [ ] Non-HTTP Activation NET-Non-HTTP-Activ Removed Through hours of searching online I have not been able to discover a resolution to the issue I am seeing. I followed the installation steps in https://woshub.com/how-to-install-net-framework-3-5-on-windows/ as this was the most complete guide. None of the suggested installation methods worked. Via Server Manager: Add roles and features -> Features -> .NET Framework 3.5 Features -> .NET Framework 3.5 (includes .NET 2.0 and 3.0 ); Using DISM: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All Using DISM: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /Source:D:\sources\sxs /LimitAccess With PowerShell: Install-WindowsFeature -Name NET-Framework-Core With PowerShell: Install-WindowsFeature -Name NET-Framework-Core -Source D:\Sources\SxS With DISM: DISM /online /Add-Package /PackagePath:D:\Sources\SxS\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab I also tried using the offline packages from my installation media without success. And when trying to use GPO to force installation from / prohibit installation from Windows Update (non-WSUS) I did not see any results. Regardless which method I use, I end up getting the same 0x800f0800 error. I've only come across https://social.technet.microsoft.com/Forums/windowsserver/en-US/5be0b03c-f499-4530-837d-76eacb4f1473/net-framework-35-cannot-install when trying to install a Windows feature, but their resolution was just rebuilding their server. This is not a viable option for my scenario. The full error from PowerShell is displayed below: PS> Install-WindowsFeature -Name NET-Framework-Core -Source D:\Sources\SxS Install-WindowsFeature : The request to add or remove features on the specified server failed. Installation of one or more roles, role services, or features failed. Error: 0x800f0800 At line:1 char:1 + Install-WindowsFeature -Name NET-Framework-Core -Source D:\Sources\SxS + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature], Exception + FullyQualifiedErrorId : DISMAPI_Error__Failed_To_Enable_Updates,Microsoft.Windows.ServerManager.Commands.AddWind owsFeatureCommand Any help on this issue is greatly appreciated! Crosspost: https://serverfault.com/questions/1134449/windows-server-2019-cannot-install-net-3-5
Windows 10 installation failed (in-place Upgrade/Repair)
Windows 10 Pro ver 22H2, MSI M=motherboard, i9, 128 GB RAM, NVMe boot disk. ** The issue is a Win10-to-Win10 in-place repair/upgrade that fails after what looks like a successful and lengthy process. Background: This is a new hardware system that started from an in-place upgrade from Win7 to Win10. The newly upgraded Win10 was a bit quirky, but worked out most of the bugs - mostly drivers, of course. But still an odd hiccup, sooo, decided to do an in-place Win 10 Upgrade/Repair, but it fails. Twice tried the in-place Upgrade with two different ISO's, one from the Media Creation Tool based on my system, and another multi-version ISO from an MS web page. What is peculiar is that the install looks like it goes perfectly well - goes thru a 20+ minute process, first in Windows, then a blue DOS-ish screen, then back to Windows. Then all of a sudden a little dialog that simply says "Windows 10 installation failed". Dont bother suggesting a clean install. That is a sick and insane idea that people throw out there like they've said something smart. Not smart. And that is because not only does all the software have to be - reinstalled, but what about all the setups and tweaks one does as they curate and caress their software. Many such tweaks on a mature system might be years old, so NO, not going thru have to figure all that out. Have tried all the tries - SFC, DISM (see note below), chkdsk, driver updates/uninstall-reinstall, virus scan, hardware stress tests. Another perhaps related peculiarity is that DISM /RestoreHealth fails with the "source files could not be found" error. Also, DISM fails after it works for a really long time, usually on 62.3%, but then comes back with the "source" error.
