Windows 7 Microsoft .NET Framework 4.5.50709

[stibbetts1]

I'm attempting to install Microsoft .NET Framework 4.5.50709 via an MDT task sequence and can't get this
to run silently for some reason. I'm using the following Quiet install command "dotnetfx45_full_x86_x64.exe /q /norestart" and that didn't work so I
added the /qb switch as shown here "dotnetfx45_full_x86_x64.exe /qb
/norestarttnetfx45_full_x86_x64.exe /qb /norestart" and it seems to get
hung up at the license terms dialogue box. Does anyone have any suggestions on
how to get this installed silently?

 

[ChatGPT]

When installing Microsoft .NET Framework 4.5.50709 silently using an MDT task sequence, you encountered issues with the installation getting stuck at the license terms dialogue box. To ensure a silent installation without any dialog boxes, you can try the following approach:

1. Check Compatibility:
- Ensure that the installation package of .NET Framework 4.5.50709 supports silent installation with the switches you are using.

2. Correct Command Syntax:
- The switches you mentioned seem correct (/q for quiet mode and /norestart to prevent an automatic restart). However, the /qb switch is generally used for a basic user interface. Instead, you should stick with /q for a completely silent installation.

3. Possible Solution:
- Try using the following command for a truly silent installation:

     dotnetfx45_full_x86_x64.exe /q /norestart

4. Logging:
- To troubleshoot installation issues, consider enabling logging. You can add a switch like /l*v log.txt to create a log file that captures installation details. This can help identify the exact point where the installation process is getting stuck.

5. Testing:
- Before deploying through MDT, try running the installation command manually on a test machine to see if it installs silently without any issues.

By following these steps and ensuring the correct command syntax, you should be able to perform a silent installation of Microsoft .NET Framework 4.5.50709 successfully. If the issue persists, reviewing the installation log can provide more insights into the problem.