.Net Native Framework Package 1.2.23205.0 keeps updating

Page 5 of 7 FirstFirst ... 34567 LastLast

  1. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #41

    SoFine409 said:
    ...
    Generally I'm very conservative with registry cleaning. I'm not shy about making individual registry edits as long I understand exactly what's the key(s) do. Since Johnpd blew a hole in my theory (in Post#38) about SDK, I'll probably just sit tight until MS fixes the issue.
    I'm with you on conservative use of registry cleaners. I trust cCleaner to not be too aggressive and clean up only the things that really are broken. In other words ... cCleaner is also very conservative.

    Cleaner lets you create a backup of all keys before you fix them.
    The option is always available to you if you get tired of waiting for MS.
      My Computer


  2. Posts : 1,524
    Win10 Pro
       #42

    Slartybart said:
    I'm with you on conservative use of registry cleaners. I trust cCleaner to not be too aggressive and clean up only the things that really are broken. In other words ... cCleaner is also very conservative.

    Cleaner lets you create a backup of all keys before you fix them.
    The option is always available to you if you get tired of waiting for MS.
    Thank you Slartybart. Your advice and reassurance is much appreciated. I overlooked the backup option. I think I will take the time to get to know cCleaner. It's been sitting on my desktop for about 6 months just waiting for me to pay attention to it! I should definitely get to know it as it sounds like another valuable tool.

    I like your sig, very true. Knowledge is the most precious gift anyone can give. Just can't beat seeing the light come on in someone's eyes when you show them something new!
      My Computers


  3. Posts : 1,524
    Win10 Pro
       #43

    Update with possible solution


    On July 1 the cycle of Net Native Framework Package 1.2.23205.0 and MS Advertising SDK for XMAL updating each day began again after about a 2 week hiatus. The updates have occurred each day through yesterday, July 7.

    After seeing a post about a similar but not the same issue, I uninstalled cCleaner yesterday afternoon and this morning there was neither a Net Native Framework update nor an MS Advertising SDK for XMAL update.

    I'll continue to monitor the situation and report back in a few days.
      My Computers


  4. Posts : 323
    Windows 10 (2), Win 8.1 (1), Win 7 (1)
       #44

    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
      My Computer


  5. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #45

    johnpd said:
    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.
      My Computer


  6. Posts : 1,524
    Win10 Pro
       #46

    Slartybart said:
    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
      My Computers


  7. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #47

    SoFine409 said:
    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
    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
    .
      My Computer


  8. Posts : 1,524
    Win10 Pro
       #48

    Slartybart said:
    You're so fine Bob
    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.
      My Computers


  9. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #49

    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

    Bill
    .
      My Computer


  10. Posts : 1,524
    Win10 Pro
       #50

    Slartybart said:
    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

    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?
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:13.
Find Us




Windows 10 Forums