Windows 10: .Net Native Framework Package 1.2.23205.0 keeps updating

Well, there ya go - answered your own good questions with equally good answers.

If there are leftovers - see if Revo uninstaller Free (scroll down to the free version on the page)
Download Revo Uninstaller Freeware

finds and cleans up the remnants.

If it's VS tools for MSO runtime, see if selecting MSO in Programs and Features > Repair helps.

All of the above is only necessary if the Net Native Framework Package is still offered as an update.

 

I have MS Office 2010 (Home and Student Edition) installed with the Visual Studio Tools Runtime for 2010. I never had Visual Studio itself installed so it did apparently get installed with Office 2010. If have attached an image below of what I have on one of my computers.

It is interesting that these two items (Office 2010 and Visual Studio Tools Runtime) indicate an installation date of 7/3/2016. I have noticed that this date gets changed for software even though no physical update occurs. There was no update for Office on that day, only one of the many .NET Native Framework updates for v1.2.23205 since 7/1. The subsequent .NET Native Framework "updates" did not change the date.

On my older Thinkpad, I have Office 2007. No Visual Studio Tools Runtime exists on it. I do not have that computer on that often so updates are not that frequent. Four updates for the .NET Native Framework Package appear for it for the period available on Reliability History (which is usually a max of one month): two for v1.2.23205 (the offending one) and two for v1.3. I also see two for the MS Advertising SDK for XAML.

So I am not sure what might be the driving force behind the continued updates of the .NET Native Framework Package v1.2.23205 and MS Advertising SDK for XAML. The other thing that I notice is that in the <User> Packages folder, v1.2 has only a .NET Native Framework package and no corresponding Runtime package while .NET Native v1.4 has no Framework package but only a Runtime package. Whether that is right or wrong, I don't know.

JohnD

 

I was reading a bit about VS tools fro MS runtime and saw that I gave the wrong steps in post# 59

If it's VS tools for MSO runtime, see if selecting MSO in Programs and Features > Repair helps.
should be
If it's VS tools for MSO runtime, see if selecting MSO in Programs and Features > Uninstall > Repair helps.

This might be a good place to start to research
Visual Studio Tools for Office Runtime Overview

If you want to try to download it fresh:
Download Visual Studio 2010 Tools for Office Runtime from Official Microsoft Download Center

Other references:
Visual Studio Tools for Office Runtime Installation Scenarios
How to: Install the Visual Studio Tools for Office Runtime Redistributable

Microsoft Visual Studio 2010 Tools for Office Runtime update
Is KB2525428 the update that keeps getting offered?

I was thinking that VS tools for MSO runtime was an optional component. It's been a while since I had MSO on my machine though. I thought that if you custom installed MSO, you had the choice to install the VS tools - I could be wrong.

Are you given the choice in Uninstall > Repair?

 

On mine the only choice is uninstall. I thought about trying and uninstall/reinstall but at this point I'm thinking it's probably only solvable from Microsoft's end.

 

Has the update been offered again after you used cCleaner ?

If the problem persists, try:
Windows Updates - Hide or Show in Windows 10 - Windows 10 Forums

 

The updates can not be hidden because they only show in Perf Monitor.

I did reinstall and initialize all of the default apps. I'll monitor the issue over the next few days to see if that helps.

UPDATE 7/13: Net Native Framework Package 1.2.23205.0 update a few minutes ago. I noticed that on one of my other PC that has VS installed, this package updated only once sometime ago. Thats interesting so its possible that if I reinstall VS on the problem PC that the upadate will happen and that will be the end of it. I honestly don't remember if VS was ever previously installed but it is entirely possible that it was. I probably won't have time to do this until Friday but I'll report back in after the new install has had a chance to settle in.

UPDATE 7/17: Reinstalled VS 2015 thinking that might fix the Net Native updated but it did not. Unless anyone else has a fix I'm just going to live with this until MS fixes the problem but I suspect that hell will freeze over first.

UPDATE 8/12: No more annoying Net Native Framework Package installs. Looks like the AU solved the problem. FYI it would appear the an upgrade in place of the previous version would have probably solved the issue as well.