Windows 10: .Net Native Framework Package 1.2.23205.0 keeps updating

FYI we had two threads running on this issue but Brink has combined them.

First, thanks to everyone who has responded, your suggestions are appreciated.

So far I’ve not been able to stop MS Advertising SDK for XAML Net Native Framework Package 1.2.23205.0. from installing every day. I did these but they haven’t help:

Ran MS FixDoNet Repair Tool
Ran WUFix.bat by TairikuOkami
Uninstalled Windows Software Development Kit

At this point I think I have 3 options unless anyone else has another suggestion. I’d like to hear opinions about which you think might be most likely to work.

1. Run the .Net Framework Cleanup Tool suggested by Essenbe. The introduction is a bit intimidating but I’ll definitely run a full backup first if I elect to do this. I’m assuming that after the tool runs and if my PC doesn’t explode, I’ll need to reinstall the necessary .Net versions beginning with the lowest version. I checked the registry and learned that I have the following versions of .Net installed.
v2.0.50727
v3.0
v3.5
v4
v4.5
If anyone has knowledge of anything that I need to know about reinstalling .Net it would be helpful.

2. Do a repair install of the OS. At this point this is probably the most appealing but I’m not sure if this would solve the problem especially it is a result of a goofy update.

3. A clean install. This is my OMG option since it’s likely to take me 2 to 3 day to reinstall all of mt software. Although I’ve done this before and have everything on hand that I’ll need, I would do this as a last resort. That said, it might be the best since I’m seeing other issues now like apps terminating (explorer, Outlook, and most recently svchost crashing (faulting module: esent.dll).

Please let me know what you think. I’m going to sit tight until I get some addition input. Thanks in advance.

 

Shouldn't you have net Framework 4.6 installed also? I know this is rather elementary, but have you looked in Programs and Features, Turn Features on and Off? Although I can't see why it would make it keep installing over and over.

 

Yes you are correct and I just finished looking at that same screen.



I also just finished running the .Net Framework Setup Tool that is mentioned in the link that you gave me and the following net packages are installed and verified:
2.0 SP1
3.0 SP2
3.5 SP1
4 Client
4 Full
4.5
4.5.1
4.5.2
4.6
4.6.1
It is a bit odd that in the Windows Features applet Net 4.6 is not checked yet the verification tool reported no problems with the 4.6 and 4.6.1 installation.

So I'm thinking that the problem is not the .Net packages after all but something else link maybe something in the updating part of the OS. Any thoughts?

 

I think you should try checking those 2 in programs and features, it seems to me they should be. When you installed the SDK did it require you or did you install the net framework listed in the kit. I had 3.0 and 3.5 installed but it insisted I install it again with the SDK.

 

You have 4.6 checked and installed, just like 3.5. ASP.NET is server side framework.

 

I uninstalled the SDK yesterday so should it matter now? I certainly worth to try but which to should I check the two WCF under 3.5?

 

I don't understand. Could you please clarify?

 

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

 

You're most welcome and thanks for the powershell code! Bob R.

 

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.

 

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!