I just checked through the registry and I don't see an entry for Net Package 1.2.23205.0 but I do see one for 1.2.23231.0 which is a more recent version. Since these are native packages they should have been installed with the OS. So maybe something has damaged them. That said I've run SFC several times but to no avail. So maybe an in-place upgrade might be the next thing to try?
I was poking around researching Net Native Framework and learned that it is code that is used by MS Universal Apps. If and app that uses one of the framework packages is deleted and leaves behind an orphaned package then it could cause problems. This is interesting since in Post # 6 AnEdge (JD) said that it was related to the MSFT Store. I was a bit skeptical but it turn out he was dead on.
Continuing on with my research, I found the following on Sysnative Forum.
https://www.sysnative.com/forums/win...untime+Package.
Basically this is a known update bug in the Windows Store and hopefully will be fixed in a future update. Thanks to everyone who responded to this and especially to AnEdge who called it right in the beginning.
Since we combined two threads, I'm no longer the original poster so I'm not able to make it as solved but having learned more about Net Native Framework then I ever wanted I'm satisfied.
Basically this is a known update bug in the Windows Store and hopefully will be fixed in a future update. Thanks to everyone who responded to this and especially to AnEdge who called it right in the beginning.
Since we combined two threads, I'm no longer the original poster so I'm not able to make it as solved but having learned more about Net Native Framework then I ever wanted I'm satisfied.[/QUOTE]
Hey SoFine, if you want to reinstall all the native apps that came with Win 10, in case you deleted some, you can run a PowerShell command as administrator with this code, courtesy of CNET
get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
Just copy and paste into the shell, hit enter and it may seem nothing is going on, wait a minute and then check your apps in the start menu to see if they all returned. This should help I think with the framework returning.
Thank you also for the shoutout, and I wish you the best JD
Last edited by AnEdge; 23 May 2016 at 17:22.
I generated the WU log for one of the days (5/19) where a duplicate install occurred and extracted some information.
From what I can decipher, it indicates the following:
1. WU downloads two items for updating:
(a) 2 "Bundles" for .NET Native Framework 1.2.23205.0:
[9F59A68F-2608-42CE-877A-4C0D66EFFBA7.1]
[25BB9E66-1B6F-48CB-8176-02A231E270A6.1]
and
(b) 3 "Bundles" for Microsoft Advertising SDK for XAML (which is another one it seems to be repeating)
[359B2C48-BB7A-4250-98E8-DA09C64EF167.1]
[20CFE861-B972-48E2-8359-766054AAAD3A.1]
[F9C36D2F-4292-485B-905B-29267D103B6A.1]
2. When it gets to the point of installing them.
(a) .NET Native Framework lists an additional item (not downloaded)
[A13F723C-03DD-47D9-AC6B-02B45DD6F41A.1] but only actually installs one of the three:
[25BB9E66-1B6F-48CB-8176-02A231E270A6.1]
(b) Microsoft Advertising SDK for XAML lists the 3 Bundles downloaded, but only installs two:
[20CFE861-B972-48E2-8359-766054AAAD3A.1]
[F9C36D2F-4292-485B-905B-29267D103B6A.1]
Is this normal for updating Apps or does this indicate what might be the problem?
JohnD
Where did you find the WU log info, I'd like to look at mine as well?
I'm curious how WU thinks that these updates are needed when obviously they are not?
The post that I found on Sysnative Forums says that an in-place install fixes this issue so something's happened to our PC's and I bet it has to do with the Developer Software that we've installed although I uninstalled mine and the issue persists.
I just posted a new thread on the Sysnative Forums about this issue and sent a message to one of the moderators BrainDrab, who is an expert on the WU process, asking for any solutions short of reinstalling all of the .Net packages or an in-place upgrade. I included the information that you developed from your WU logs. Maybe we'll get lucky and find a fix.
BTW, I've been to Green Valley many times. When I worked at the Smithsonian I made regular visits to the observatory on Mt. Hopkins near Amado. I started staying in Green Valley in lieu of Tucson. Great part of the country. Maybe when my wife retires I can come live in the Valley.
Last edited by SoFine409; 24 May 2016 at 10:48. Reason: added info
The file needs to be generated from a series of Event Tracing files (.etl). This can be done using Powershell. Here is a link describing how to do it: Generating Windows Update Log Files
Read the instructions carefully, especially about waiting until you get the final message that it has written the log to your desktop. The file is not easy reading.
Being an amateur astronomer, I found that the Green Valley area is an outstanding location for viewing the night sky. Since Green Valley is close to the observatory, there are lighting restrictions in place to cut down light pollution. Our club actually uses the Whipple Observatory Visitor's Center to do some observing.
JohnD
My, my, it is a small world. I've been an amature astronomer all my life. Having SAO as I client during my 35 years at the Smithsonian gave me an opportunity to meet lots of researchers at SAO and the U of A. Do you know Dan Brocious? I think he's with IDA now. Stayed on the mountain several times and had opportunities to visit some of the instruments during observing. Watched the MMT evolve over the years. We use to have the base camp in the old Amado school house for many years. What a dump that was!
I know Dan. He used to provide public star parties at Whipple several times a year. Unfortunately when he retired, Whipple never kept the star parties going. They used to get big crowds.
JohnD
Since 5/24 neither of the two packages have installed again. I suspect that it might have been solved by an update to one of these apps:
Moves & TV
OneNote
3D Builder (updated two times)
Mail and Calendar
Office 15 Click-to-Run Components (four of them)
Sway
Please let me know if this has happened to you as well.
Earlier this morning, BrianDrab, one of the moderators on the Sysnative Windows Update Forum, responded to my earlier post with the follow.
"Hi and welcome to Sysnative. I don't believe there is any known resolution to this. It's a minor benign annoyance. This happens on all of the Windows 10 machines at my work. Let me take a look however and see if I can come up with anything. I'll be back with you."
It looks like this is not something to be over worried about. We should nonetheless continue to note and new development on this issue.
Quote
