Windows 10: .Net Native Framework Package 1.2.23205.0 keeps updating

I don't have cCleaner installed on any system so that is not the problem with me. I finally upgraded my main computer late last month. Since July 1st I have received the .Net Framework update almost every day on that computer. I received the Advertising SDK only twice since then. I don't know what to think at this point.

JohnD

 

I'm not sure why uninstalling cCleaner resolved the issue for SoFine409 - the only thing I could guess is an old cCleaner got carried over in the upgrade, but I don't think cCleaner use .Net.

More importantly, .NET v1 has been depreciated ... and ... the cCleaner Registry feature flags .NET v1 as something to correct.

If you try what I suggested in post# 37 I believe that should resolve the issue for you.

Amendment to post# 37 - run the Registry scan again until there are no additional issues found in a scan.

 

Hi Slartybart and thanks for your response. cCleaner was definitly not the problem as the Native Net Framework and SDK updates strated installing again yesterday and today. I took your advise and used cCleaner to remove 38 Missing Shared DLLs related to Net Framework V1.0 and 1.1 and I'll monitor the situation over the next few days and let you know what happens. Fingers crossed!
Bob

 

You're so fine Bob *Wink
Thanks - post your findings to help other members

It's possible that some software on your machine has .NET v1.x in it's manifest. Time to update that software if that is the case - we'll see in a few days, eh wot.

Bill
.

 

I've been thinking about that as well.
I have Calendar Creator V9 by Broderbund. It dates from the Win98 era and could very be the the culprit. If the issues persist after the registry celeaning I'll try uninstall it.

 

You'll either know right away if the culprit complains about not finding .NET v1.x or Win10 .NET 4.6 resolves the dependency for .NET v1.x

I just checked Broderbund, calendar creator is up to v12.1 - but it's not free
There was not any .NET dependency on the requirements page.

I wouldn't try to figure out what might depend on .NET v1.x - the culprit program will let you know or not run at all the next time you launch it. If no program complains, then don't sweat it *Wink

Bill
.

 

We might be barking up the wrong tree. NET FRAMEWORK is different than NET NATIVE FRAMEWORK. The later is something that MS just developed for cross platform compatibility. Some of the folks over on Sysnative Forums told me a while back that this was a windows store bug. I had forgotten all about that, old age does that! So maybe it's just another MS issue that will get solved at some future date?

 

Well .... old age also makes you see NET FRAMEWORK when NET NATIVE FRAMEWORK is written

Thanks for pointing it out - I try to read things as they are written, but the brian does what it wants with it. *Biggrin

How many of each kind of animal did Moses bring on the ark?

 

Probably a lot more than 2 since I'm sure that all got hungry <grin>!

 

Who was on the ark?
*Roflmao2
I don't think it was Moses - some other guy perhaps

The mind is a crazy place

 

I kept looking at the question trying to figure out what about it was not right. Another 2 weeks and I would have gotten it!
*Doh

 

You know it was Noah, not Moses - right?
You did get 2 right though - sort of. I'm not sure they brought more than two of each kind though
- they probably ate the pairs of tasty animals *Eek
I'd hate to cause 2 weeks of mind bending over one How the mind gets things wrong

I guess it's time to get serious again, in case someone visiting the thread thinks:
Am I still on Tenforums or did I somehow get to the Bedlam Royal Hospital site

I enjoyed our chat - thanks again for pointing out my reading error (I'd be crooked if other people didn't keep me honest).
If the update issue crops up again - we can take a different tact
- one that directly addresses NET NATIVE FRAMEWORK *Cool

 

Yes the .NET Native Framework relates to the Windows Universal Apps, not the standard software that uses .NET Framework. It resides in
"C:\Users\{user name}\AppData\Local\Packages" not in the "C\Windows\Microsoft.Net" area. The Universal App updates are separate from the standard Windows Updates and do not appear in the Windows Update History. It only shows in the Reliability Monitor.

JohnD

 

You might need to update Visual Studio if it is installed

What's new for the .NET Native Compiler and Runtime in Visual Studio 2015 Update 2 | .NET Blog

Downloads | Visual Studio

 

Good thought but I don't have VS installed on the problem PC. I have it on two other PCs but they're not experiencing the never ending updates. It does however have Microsoft Visual Studio 2010 Tools for Office Runtime (x64). I wonder how I got that? I do have Office 2013 so I'm thinking it's installed with office. Maybe I did have VS installed at one time and then uninstalled it and the runtime was leftover. That could explain why I'm getting the SDK for XMAL updates as well.
Update: it is in fact installed with Office 2010 and 2013.