Answered by:
ISSUE: Win2019 Server .Net 3.5

Question
-
I'm trying to setup and endpoint AV solution on its own 2019 VM. The software requires .Net 3.5.
On a clean Hyper-V installation of Windows 2019 Server, literally nothing else installed, .Net 3.5 fails to install. In fail I mean it halts and sits endlessly until I shut the VM down and I force it to restart.
I've attempted the installation by selecting .Net 3.5 as a Windows 2019 Role.
I've also downloaded a 240MB full install and tried it by specifying a local source folder.
No matter how I approach this the end result is the same, the progress bar goes about 1/2 way and stays there indefinitely.
- Edited by CalvaryIT Tuesday, September 17, 2019 12:16 AM
- Moved by Dave PatrickMVP Tuesday, September 17, 2019 2:10 AM .Net setup issues
Tuesday, September 17, 2019 12:15 AM
Answers
-
You need an installation media, then specify an alternate source path to the installation media source\sxs folder, install.
Or, use dism /online /Add-Package /PackagePath:[sourcepath] command to offline install.
https://sysmanrec.com/installing-net-framework-3-5-on-server-2019-fails
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Marked as answer by CalvaryIT Tuesday, September 17, 2019 7:48 PM
Tuesday, September 17, 2019 3:05 AM
All replies
-
You should insert installation media when you install .Net 3.5 by using Server Manager features,
Refer,
Tuesday, September 17, 2019 1:58 AM -
You need an installation media, then specify an alternate source path to the installation media source\sxs folder, install.
Or, use dism /online /Add-Package /PackagePath:[sourcepath] command to offline install.
https://sysmanrec.com/installing-net-framework-3-5-on-server-2019-fails
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Marked as answer by CalvaryIT Tuesday, September 17, 2019 7:48 PM
Tuesday, September 17, 2019 3:05 AM -
That makes sense. However, the original Windows 2019 installation was from a local image on a local drive to that VM. Would not the path to the installation source files be resident in that servers configuration for instances such as this?
- Edited by CalvaryIT Tuesday, September 17, 2019 3:49 PM
Tuesday, September 17, 2019 4:28 AM -
You may need to send the sxs folder into a cloud storage, then download it in VM from cloud storage.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Tuesday, September 17, 2019 6:17 AM -
Okay, back at my desk. I'll give this a shot and let you know how it goes later today.
This seems like a lot of consideration and work for something that should be very straightforward, aka the easy stuff.
Tuesday, September 17, 2019 3:59 PM