Menu
CCMEXEC.COM – Enterprise Mobility
  • Home
  • General
  • Configuration Manager
  • Windows 10
  • Intune
  • GitHub
  • Windows 11
  • About the author
CCMEXEC.COM – Enterprise Mobility

Excluding .Net Framework 4.6.1 when building a reference image

Posted on February 3, 2016August 25, 2017 by Jörgen Nilsson

I have written some posts before on how to block updates if you build your images using MDT or SCCM for that matter and download the update using ZTIwindowsupdate.wsf directly from Internet instead of installing a dedicated WSUS which I always recommend, https://ccmexec.com/2013/09/tips-when-building-images-with-configmgr-2012-part-2/ I got a couple of questions on how to block .Net Framework 4.6.1 when building Windows 7 images.

On January the 26th .NET Framework 4.6.1 was released on Windows Update as a recommended update for Windows 7 and Server 2008 R2, If you build your images and install updates from Windows Update you will now get .NET Framework 4.6.1 installed.

You can block it using the normal way and block KB3102433 as shown below either in Customsettings.ini or as a Task Sequence variable in SCCM.

BlockNet

Or you can use the registry key to block the installation then .NET Framework 4.6.1 will not be installed after the image is deployed either. So in some scenarios that can be a good solution.. By running the following command in the Task Sequence before the ZTIWindowsUpdate.wsf step will block the installation. More information can be found here: https://support.microsoft.com/sv-se/kb/3133990

reg add “HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\WU” /v “BlockNetFramework461” /d “1” /t REG_DWORD /f

If you then want to enable the installation again and you mange your updates through WSUS or Configuration Manager you can remove the registry key in the task sequence after software updates are installed with the following command.

reg delete “HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\WU” /v “BlockNetFramework461” /f

Both solutions will do the job!

 

  • Configuration Manager
  • Master Image
  • Reference Image
  • SCCM
  • 1 thought on “Excluding .Net Framework 4.6.1 when building a reference image”

    1. Pingback: MDTSCCM – ne pas ajouter les .net 4.6.1 à une image de référence. – Les2t.fr Blog IT – TRARBACH Jean-Yves et THONON Stéphane

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    My name is Jörgen Nilsson and I work as a Senior Consultant at Onevinn in Malmö, Sweden. This is my blog where I will share tips and stuff for my own and everyone elses use on Enterprise Mobility and Windows related topics.
    All code is provided "AS-IS" with no warranties.

    Tweets by ccmexec

    Recent Posts

    • Windows Servicing, Personal Teams and Success.cmd
    • Windows MDM Security Baseline – Settings Catalog
    • Configuring MS Edge Security Baseline v107 using Settings Catalog
    • Configuring Desktop App Installer using CSP and script?!
    • Customizing Taskbar and Start in Windows 11 22h2 with PowerShell

    ©2023 CCMEXEC.COM – Enterprise Mobility | WordPress Theme by Superb Themes
    This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.Accept Reject Read More
    Privacy & Cookies Policy

    Privacy Overview

    This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
    Necessary
    Always Enabled
    Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
    Non-necessary
    Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
    SAVE & ACCEPT