.NET Framework 4.8 is available on Windows Update, WSUS and MU Catalog

38 comments

Discussion is closed. Login to edit/delete existing comments.

• 

  Barry Obie December 12, 2019 0

  Collapse this comment Copy link

  Oh man. I spent hours trying to figure out why 4.8 wasn’t showing in my WSUS updates for 2016 Servers. It wasn’t until I read through these comments that I discovered that was “by design.” I wish it was documented somewhere that was the case. I couldn’t understand why every where it said it was available on WSUS. I thought I had something misconfigured. But nope! Just “by design.”

• 

  Mario Volarevic November 27, 2019 0

  Collapse this comment Copy link

  Since .NET 4.8 was updated via Windows Update on the machines in our company and our customers we are having serious issues with our WPF application which uses Infagistics controls.
  In some cases on refresh of the control (when notify changed is called) because Selected is not found (partial stack trace is posted below, 4 methods from our code are not included).
  Based on the behaviour it seems like something gets messed up in the...

  Read more

  Since .NET 4.8 was updated via Windows Update on the machines in our company and our customers we are having serious issues with our WPF application which uses Infagistics controls.
  In some cases on refresh of the control (when notify changed is called) because Selected is not found (partial stack trace is posted below, 4 methods from our code are not included).
  Based on the behaviour it seems like something gets messed up in the ordering of layouting, rendering, displaying and selecting the data (like Dispatcher triggers in the wrong order).
  As soon as we uninstall the .NET 4.8 update, issue is not happening anymore.

  | System.InvalidOperationException: ‘Selected’ name cannot be found in the name scope of ‘System.Windows.Controls.ControlTemplate’.
  | at System.Windows.Media.Animation.Storyboard.ResolveTargetName(String targetName, INameScope nameScope, DependencyObject element)
  | at System.Windows.Media.Animation.Storyboard.ClockTreeWalkRecursive(Clock currentClock, DependencyObject containingObject, INameScope nameScope, DependencyObject parentObject, String parentObjectName, PropertyPath parentPropertyPath, HandoffBehavior handoffBehavior, HybridDictionary clockMappings, Int64 layer)
  | at System.Windows.Media.Animation.Storyboard.ClockTreeWalkRecursive(Clock currentClock, DependencyObject containingObject, INameScope nameScope, DependencyObject parentObject, String parentObjectName, PropertyPath parentPropertyPath, HandoffBehavior handoffBehavior, HybridDictionary clockMappings, Int64 layer)
  | at System.Windows.Media.Animation.Storyboard.BeginCommon(DependencyObject containingObject, INameScope nameScope, HandoffBehavior handoffBehavior, Boolean isControllable, Int64 layer)
  | at System.Windows.Media.Animation.BeginStoryboard.Begin(DependencyObject targetObject, INameScope nameScope, Int64 layer)
  | at System.Windows.StyleHelper.InvokeEventTriggerActions(FrameworkElement fe, FrameworkContentElement fce, Style ownerStyle, FrameworkTemplate frameworkTemplate, Int32 childIndex, RoutedEvent Event)
  | at System.Windows.StyleHelper.ExecuteEventTriggerActionsOnContainer(Object sender, RoutedEventArgs e)
  | at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
  | at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
  | at Infragistics.Windows.DataPresenter.DataRecordCellArea.OnRecordPropertyChanged(Object sender, PropertyChangedEventArgs e)
  | at Infragistics.Windows.DataPresenter.DataRecordCellArea.System.Windows.IWeakEventListener.ReceiveWeakEvent(Type managerType, Object sender, EventArgs e)
  | at System.Windows.WeakEventManager.ListenerList.DeliverEvent(Listener& listener, Object sender, EventArgs args, Type managerType)
  | at System.Windows.WeakEventManager.ListenerList`1.DeliverEvent(Object sender, EventArgs e, Type managerType)
  | at System.ComponentModel.PropertyChangedEventManager.OnPropertyChanged(Object sender, PropertyChangedEventArgs args)
  | at System.ComponentModel.PropertyChangedEventHandler.Invoke(Object sender, PropertyChangedEventArgs e)
  | at Infragistics.PropertyChangeNotifier.OnPropertyChanged(String propertyName)
  | at Infragistics.Windows.DataPresenter.DataPresenterBase.UpdateSelectedItems(SelectedItemHolder selected)
  | at Infragistics.Windows.DataPresenter.DataPresenterBase.SelectNewSelection(Type type, SelectedItemHolder selected)
  | at Infragistics.Windows.DataPresenter.DataPresenterBase.InternalSelectItem(ISelectableItem item, Boolean clearExistingSelection, Boolean select)
  | at Infragistics.Windows.DataPresenter.Record.set_IsSelected(Boolean value)

  Read less
  • 

    Arpit Dev Mathur December 12, 2019 0

    Collapse this comment Copy link

    Hi Mario, thanks for the bug report!

    Can you please file a Github issue at https://github.com/dotnet/wpf

    Please include the following in your issue.

    A sample application that reproduces the issue
    OS versions that you are seeing this on
    Whether the 4.8 upgrade is a patch to an existing 4.8 installation or an upgrade from 4.7.2 to 4.8

• 

  Luiza Capatina November 13, 2019 0

  Collapse this comment Copy link

  Hi,

  Since the last update of .Net Framework 4.8, namely KB4519568, My Desktop application built in C #, with WPF and WinForms through Visual Studio crash twice a day at about the same time. Stations that do not have this update have absolutely no problem. The application is targeting .NetFramework 4.7.2, although I have compiled it on 4.8. so it happens.
  The last time I had such a problem was in the .NetFramework 4.7.2 update, but...

  Read more

  Hi,

  Since the last update of .Net Framework 4.8, namely KB4519568, My Desktop application built in C #, with WPF and WinForms through Visual Studio crash twice a day at about the same time. Stations that do not have this update have absolutely no problem. The application is targeting .NetFramework 4.7.2, although I have compiled it on 4.8. so it happens.
  The last time I had such a problem was in the .NetFramework 4.7.2 update, but I compiled it on 4.7.2 and it didn’t crash anymore.
  Have you been through such a situation?
  The error that occurs is in EventViewer:
  Faulting application name: Presentation.exe, version: 1.0.0.0, time stamp: 0x5db942cd
  Faulting module name: System.Windows.Forms.ni.dll, version: 4.8.4042.0, time stamp: 0x5d7a9e88

  All the best,
  Luiza Capatina

  Read less
• 

  Lapter, Adi November 3, 2019 0

  Collapse this comment Copy link

  Is there anyway to downgrade back to .Net 4.7 after this update was done? I have tried to downgrade but in the registry I still have .net 4.8.
  Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client\1033 (version)

• 

  Sebastian Rübesamen October 1, 2019 0

  Collapse this comment Copy link

  It looks like

  “Microsoft .NET Framework 4.8 for Windows 10 Version 1607 and Server 2016 for x64 (KB4486129)”

  and

  “Microsoft .NET Framework 4.8 for Windows 10 Version 1607 (KB4486129)”

  are not published in WSUS but for newer Windows 10 versions they are – is there a special reason for that or was it just left out by mistake?

  • 

    Namrata Karnam Author October 16, 2019 0

    Collapse this comment Copy link

    Hi Sebastian, responding to you and others with similar questions – yes some of the updates are catalog only by design and not available on WSUS. Please see the Knowledge Base Articles section in the blog above for clarity on which ones are Catalog only.

    • 

      John Curtiss November 11, 2019 0

      Collapse this comment Copy link

      why? what is the “design”?

    • 

      sky November 12, 2019 0

      Collapse this comment Copy link

      it means currently the upgrade is too buggy to fit many environments (like exchange). so you need to do it yourself if you want for windows server 2016/2019. Microsoft just let it go for old windows for testing and feedback.

• 

  Michael Gorn September 19, 2019 0

  Collapse this comment Copy link

  There's a serious bug in .NET 4.8 and it's fully described here: https://social.technet.microsoft.com/Forums/windowsserver/en-US/a563b4e2-67d0-4f96-a10e-5136bc86521b/failover-cluster-manager-bug-on-server-2019-after-net-48-installed-unable-to-type-more-than-two

  Basically, after installing .NET 4.8 on Windows Server 2019 and rebooting, you are no longer able to input IPs that have 3 digits in any of the octets, into the Create Cluster Wizard (after installing Failover Clustering). Are you aware of this bug? Can you please create a KB article on it?

  Read more

  There’s a serious bug in .NET 4.8 and it’s fully described here: https://social.technet.microsoft.com/Forums/windowsserver/en-US/a563b4e2-67d0-4f96-a10e-5136bc86521b/failover-cluster-manager-bug-on-server-2019-after-net-48-installed-unable-to-type-more-than-two

  Basically, after installing .NET 4.8 on Windows Server 2019 and rebooting, you are no longer able to input IPs that have 3 digits in any of the octets, into the Create Cluster Wizard (after installing Failover Clustering). Are you aware of this bug? Can you please create a KB article on it?

  Read less
  • 

    Namrata Karnam Author February 24, 2020 0

    Collapse this comment Copy link

    Update on this – this fix was released late Jan 2020.

  • 

    Namrata Karnam Author September 26, 2019 0

    Collapse this comment Copy link

    Thanks for reporting this Michael! We were able to repro this on our end as well and are working to find the root cause. I will provide an update as soon as I have it.

    • 

      sky October 2, 2019 0

      Collapse this comment Copy link

      Thanks a lot for your effort. I never see Microsoft person answering hard questions in internet. maybe you are the only one. please keep the great work going on…

    • 

      Namrata Karnam Author October 15, 2019 0

      Collapse this comment Copy link

      We are currently working on a fix for this issue and will keep you posted on it. Thanks again for reporting it!

    • 

      Michael Gorn November 12, 2019 0

      Collapse this comment Copy link

      @Namrata Do you have an approximate timeline on when the fix will be released? Thank you.

• 

  Calum Hodgetts August 30, 2019 0

  Collapse this comment Copy link

  When will .NET Framework 4.8 be available in the update catalog and WSUS for Server 2016 and 2019?

  • 

    Namrata Karnam Author September 4, 2019 0

    Collapse this comment Copy link

    Hi Calum, it is available now. For convenience, catalog links for WS 2016 and 2019 are referenced in the Knowledge Base Articles section of the blogpost above.

    • 

      Phil Morrow September 18, 2019 0

      Collapse this comment Copy link

      I’m with Mike here. All 4.8 packages show in WSUS EXCEPT those targeting server 2016 or server 2019…. what’s up with that. I’d rather not load them manually. Why doesn’t the normal WSUS syncs pick this up? We’re getting all other 2016 and 2019 server updates.

    • 

      Calum Hodgetts September 20, 2019 0

      Collapse this comment Copy link

      I was tired of waiting so I just imported them to my WSUS so SCCM would pick them up. Looks like they were published to the catalog but not to WSUS, which means the "master list" here is wrong again as it states "Target platforms: Windows Server 1903, Windows 10 Version 1903, Windows Server 2019, Windows 10 Version 1809, Windows 10 Version 1803, Windows Server 2016, Windows 10 Version 1709, Windows 10 Version 1703,...

      Read more

      I was tired of waiting so I just imported them to my WSUS so SCCM would pick them up. Looks like they were published to the catalog but not to WSUS, which means the “master list” here is wrong again as it states “Target platforms: Windows Server 1903, Windows 10 Version 1903, Windows Server 2019, Windows 10 Version 1809, Windows 10 Version 1803, Windows Server 2016, Windows 10 Version 1709, Windows 10 Version 1703, Windows 10 Version 1607, Windows 10 Version 1511, and Windows 10 Version 1507”.

      Read less
    • 

      Namrata Karnam Author September 26, 2019 0

      Collapse this comment Copy link

      So sorry for the delay folks! We do care about this issue and are working with our WSUS team to get to the bottom of this. Will keep you all posted.

    • 

      Mike Estes September 23, 2019 0

      Collapse this comment Copy link

      Thank you Phil and Calum, good to know that I wasn't mistaken in my finding. Sad to know that it doesn't seem that they care to even respond here or on Twitter about fixing this issue on their side.

      WU is getting sadder and sadder every month, we're now finding several servers each month that say they're fully up to date but are not and requires some heavy modifications of the WU data to fix....

      Read more

      Thank you Phil and Calum, good to know that I wasn’t mistaken in my finding. Sad to know that it doesn’t seem that they care to even respond here or on Twitter about fixing this issue on their side.

      WU is getting sadder and sadder every month, we’re now finding several servers each month that say they’re fully up to date but are not and requires some heavy modifications of the WU data to fix. Most all of the biggest problems are with our Server 2016 updates, wish we hadn’t used that at all anywhere as these are the most painful to keep up to date with updates taking a long time, failing multiple times, Windows Server 2016 spontaneously rebooting on their own post install of updates, etc.

      Read less
    • 

      Mike Estes September 16, 2019 0

      Collapse this comment Copy link

      It is not yet showing up on WSUS for 2016 and 2019, I only see the updates. It is only showing up for 2012 R2, along with the updates, where it set to be important so it installed by default last month.

      We now have had our 2012 R2 boxes out of sync with 2016 and 2019 for a month now and it looks like another month since I still don’t see it showing up for 2016 and 2019 as of Sept 16th.

• 

  Matt Willing August 22, 2019 0

  Collapse this comment Copy link

  I am also experiencing the last WPF bug (the issue with the Naming page in Visual Studio) but I have .NET 4.8 installed, it seems.
  I have the latest Windows version (Version 1903, OS build 18362.295) and .NET Framework 4.8 (the .NET Framework Release code in the registry is 528040). If I click on the links at the top of this article, the installer runs and unpacks its files and then informs me that the...

  Read more

  I am also experiencing the last WPF bug (the issue with the Naming page in Visual Studio) but I have .NET 4.8 installed, it seems.
  I have the latest Windows version (Version 1903, OS build 18362.295) and .NET Framework 4.8 (the .NET Framework Release code in the registry is 528040). If I click on the links at the top of this article, the installer runs and unpacks its files and then informs me that the installation will not occur because “.NET Framework 4.8 or a later update is already installed on this computer.”
  The IDE still crashes with an ArgumentNullException “at System.Windows.Automation.Peers.DataGridItemAutomationPeer..ctor”
  Any other suggestions for resolving this issue?

  Read less
  • 

    Namrata Karnam Author September 4, 2019 0

    Collapse this comment Copy link

    The update for 1903 is available here: KB4511555. Can you try with this please?

• 

  Jim Wooley August 21, 2019 0

  Collapse this comment Copy link

  What version of the 4.8 update solves the last WPF bug (specifically for Visual Studio’s Naming styles window)? I have 1902 with the latest available 4.8 update (from July) and the bug still appears to be there for me. Is the Aug update not available yet?

  • 

    Namrata Karnam Author August 21, 2019 0

    Collapse this comment Copy link

    This fix is included in the latest update. Please install from the links at the beginning of this post to get it. 

    • 

      Michael Kopljan August 22, 2019 0

      Collapse this comment Copy link

      VS still crashes!

• 

  Mikael Aspehed August 21, 2019 0

  Collapse this comment Copy link

  Hi,
  Does the .NET Framework 4.8 have any pre-reqs on Windows 7 SP1?
  Looking at it in SCCM, the Windows 7 clients do not tag it as required and therefore don’t see it when it is deployed on them.

  BR
  Mikael

  • 

    Namrata Karnam Author August 21, 2019 0

    Collapse this comment Copy link

    Yes the D3DCompiler package is a pre-req but its included as part of the Windows update for Win 7 SP1 and installed accordingly. If you need to install the standalone package, you can download it from the Microsoft Update Catalog site. There is more information about this package available in this support article. 

    Read more

    Yes the D3DCompiler package is a pre-req but its included as part of the Windows update for Win 7 SP1 and installed accordingly. If you need to install the standalone package, you can download it from the Microsoft Update Catalog site. There is more information about this package available in this support article. 

    Read less