Metadata staging failed, result=0x80070490 for container '{564E4238-4832-4447-5633-5CB9010C3444}', DeviceSetupManager id 131.' If you happen to know what this means, please help me with this error

First and foremost, this shouldn't happen, but it does and MS doesn't give a rat's **** who suffers from it. The only thing I could do was keep trying to do restore dates to a time when the offending (I call it a fukupdate) had not been installed. You can't do this through Windows because the fukupdate file keeps crashing your system before you can complete the restore process.

• There are two ways you can do this. One way is easy, the other is difficult. I had to do the difficult process because I have programs installed on my computer that I don't want to have to reinstall. So I needed to find a way to successfully restore my computer to an earlier date before the fukupdate was installed.
• The easy way is to do an image restore or an entirely new installation. If you're able to do this, and you have sufficient backups of your important files, this is the way to go.

IMPORTANT NOTE:

Before attempting this, it would be very helpful if you have another computer adjacent running the same Windows as the one you're trying to restore, so you can refer to it when you run into problems (and you will most likely run into problems). Every situation is different, so the problems I experienced may not be the same problems you encounter.

• Must have or create a system or install or repair disk by CD, DVD or flash drive and have your DOS system to boot to it, will usually need to hit the space bar when the system is booting it will say, hit any key to boot from...
• Once in DOS repair mode, you will probably suffer a hellish experience, like I did while attempting to do a system restore point. It took me a long time (several days) and several attempts.
• The files that are essential to running the system are still corrupted, so you can't do this on Windows. You need to:

1. Boot into system repair mode from your installation or repair disc
2. Choose the number that gets you into the DOS command (cmd) mode
3. At the prompt, type a CHKDSK command in the command prompt and press “Enter”. Include parameters like “/f”, “/r”, and “/x” to scan and repair any errors. Note: If you opt to only scan your PC for drive errors, type “chkdsk” and press “Enter”.

• Once the disc is repaired, you can attempt a restore point again. Remember to pick a date before the fukupdate file was installed.
• You will probably need to do the system restore from the DOS repair mode as well. You can try to do it in Windows, but when I tried, it kept crashing before restore could complete.
• If the restore point process does not complete, it means the chkdsk did not repair the files completely and so you have to try again by rebooting into the system disk. Everything needs to be done in DOS because Windows keeps crashing and there's not enough time to do it through Windows.

Once you've been able to do a system restore successfully, you will need to turn OFF Windows update and keep that off as long as you can because as soon as it starts updating again, you are back in hell. Again, since MS doesn't give a **** about you and me and the hell we have been forced to endure, we are essentially on our own.

Because of this, we are basically "at war" with MS and the system they have created and if you know anything about being at war with anyone or anything, the only rules you are obligated to follow are the rules of survival. So do whatever you need to do to survive and keep your system running as long as you can.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Device Metadata]

"PreventDeviceMetadataFromNetwork"=dword:00000001

Copy the above to notepad, save a a file.reg and click to install it on your machine

Or

https://www.askwoody.com/wp-content/uploads/2024/09/exportkey.reg

Download that file and click to import it.

Once I did that the errors went away.

I’ve learned that the metadata address that the link refers to is actually an alias that can resolve to a whole multitude of servers across the globe - some of them appear to be less responsive than others.

I guess the network of metadata servers has become too large to manage effectively

You're referring to a CDN. I have no doubt they would utilize one. As does any other content provider or high traffic site. It appears that none of the name servers for that domain are reachable or responding.

Rule #1 Make sure that the authoritative name servers for a domain actually give correct *or ANY* responses to queries...

We can see the authoritative name servers according to the registry.....

Domain Name: trafficmanager.net Registry Domain ID: 267485169_DOMAIN_NET-VRSN Registrar WHOIS Server: whois.markmonitor.com Registrar URL: http://www.markmonitor.com Updated Date: 2023-08-28T14:50:31+0000 Creation Date: 2005-11-25T00:16:41+0000 Registrar Registration Expiration Date: 2025-11-25T00:00:00+0000 Registrar: MarkMonitor, Inc. Registrar IANA ID: 292 Registrar Abuse Contact Email: ******@markmonitor.com Registrar Abuse Contact Phone: +1.2086851750 Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited) Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited) Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited) Domain Status: serverUpdateProhibited (https://www.icann.org/epp#serverUpdateProhibited) Domain Status: serverTransferProhibited (https://www.icann.org/epp#serverTransferProhibited) Domain Status: serverDeleteProhibited (https://www.icann.org/epp#serverDeleteProhibited) Registry Registrant ID: Registrant Name: Domain Administrator Registrant Organization: Microsoft Corporation Registrant Street: One Microsoft Way, Registrant City: Redmond Registrant State/Province: WA Registrant Postal Code: 98052 Registrant Country: US Registrant Phone: +1.4258828080 Registrant Phone Ext: Registrant Fax: +1.4259367329 Registrant Fax Ext: Registrant Email: domains@microsoft.com Registry Admin ID: Admin Name: Domain Administrator Admin Organization: Microsoft Corporation Admin Street: One Microsoft Way, Admin City: Redmond Admin State/Province: WA Admin Postal Code: 98052 Admin Country: US Admin Phone: +1.4258828080 Admin Phone Ext: Admin Fax: +1.4259367329 Admin Fax Ext: Admin Email: domains@microsoft.com Registry Tech ID: Tech Name: MSN Hostmaster Tech Organization: Microsoft Corporation Tech Street: One Microsoft Way, Tech City: Redmond Tech State/Province: WA Tech Postal Code: 98052 Tech Country: US Tech Phone: +1.4258828080 Tech Phone Ext: Tech Fax: +1.4259367329 Tech Fax Ext: Tech Email: msnhst@microsoft.com Name Server: tm1.dns-tm.com Name Server: tm2.dns-tm.com Name Server: tm2.edgedns-tm.info Name Server: tm1.edgedns-tm.info DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2024-05-30T04:30:44+0000 <<<

Seeing as how they are literally the SOA for the domain, they would surely have the correct records......

phiber at devnull in ~ 

$ whois trafficmanager.net | grep 'Name Server: ' | tr "[A-Z]" "[a-z]" | cut -d ':' -f 2 | sort -u | while read NS; do dig -t A devicemetadataservice.trafficmanager.net @$NS; done 

; <<>> DiG 9.18.27 <<>> -t A devicemetadataservice.trafficmanager.net @tm1.dns-tm.com 

;; global options: +cmd 

;; Got answer: 

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61068 

;; flags: qr aa rd ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 

;; WARNING: recursion requested but not available 

;; OPT PSEUDOSECTION: 

; EDNS: version: 0, flags:; udp: 1232 

;; QUESTION SECTION: 

;devicemetadataservice.trafficmanager.net. IN A 

;; AUTHORITY SECTION: 

trafficmanager.net.     30      IN      SOA     tm1.dns-tm.com. hostmaster.trafficmanager.net. 2003080800 900 300 2419200 30 

;; Query time: 46 msec 

;; SERVER: 150.171.10.240#53(tm1.dns-tm.com) (UDP) 

;; WHEN: Thu May 30 01:08:21 EDT 2024 

;; MSG SIZE  rcvd: 130 

; <<>> DiG 9.18.27 <<>> -t A devicemetadataservice.trafficmanager.net @tm1.edgedns-tm.info 

;; global options: +cmd 

;; Got answer: 

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52160 

;; flags: qr aa rd ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 

;; WARNING: recursion requested but not available 

;; OPT PSEUDOSECTION: 

; EDNS: version: 0, flags:; udp: 1232 

;; QUESTION SECTION: 

;devicemetadataservice.trafficmanager.net. IN A 

;; AUTHORITY SECTION: 

trafficmanager.net.     30      IN      SOA     tm1.dns-tm.com. hostmaster.trafficmanager.net. 2003080800 900 300 2419200 30 

;; Query time: 39 msec 

;; SERVER: 13.107.222.240#53(tm1.edgedns-tm.info) (UDP) 

;; WHEN: Thu May 30 01:08:21 EDT 2024 

;; MSG SIZE  rcvd: 130 

; <<>> DiG 9.18.27 <<>> -t A devicemetadataservice.trafficmanager.net @tm2.dns-tm.com 

;; global options: +cmd 

;; Got answer: 

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10029 

;; flags: qr aa rd ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 

;; WARNING: recursion requested but not available 

;; OPT PSEUDOSECTION: 

; EDNS: version: 0, flags:; udp: 1232 

;; QUESTION SECTION: 

;devicemetadataservice.trafficmanager.net. IN A 

;; AUTHORITY SECTION: 

trafficmanager.net.     30      IN      SOA     tm1.dns-tm.com. hostmaster.trafficmanager.net. 2003080800 900 300 2419200 30 

;; Query time: 46 msec 

;; SERVER: 150.171.16.240#53(tm2.dns-tm.com) (UDP) 

;; WHEN: Thu May 30 01:08:21 EDT 2024 

;; MSG SIZE  rcvd: 130 

; <<>> DiG 9.18.27 <<>> -t A devicemetadataservice.trafficmanager.net @tm2.edgedns-tm.info 

;; global options: +cmd 

;; Got answer: 

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13455 

;; flags: qr aa rd ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 

;; WARNING: recursion requested but not available 

;; OPT PSEUDOSECTION: 

; EDNS: version: 0, flags:; udp: 1232 

;; QUESTION SECTION: 

;devicemetadataservice.trafficmanager.net. IN A 

;; AUTHORITY SECTION: 

trafficmanager.net.     30      IN      SOA     tm1.dns-tm.com. hostmaster.trafficmanager.net. 2003080800 900 300 2419200 30 

;; Query time: 46 msec 

;; SERVER: 13.107.206.240#53(tm2.edgedns-tm.info) (UDP) 

;; WHEN: Thu May 30 01:08:21 EDT 2024 

;; MSG SIZE rcvd: 130

OOF!

Upon closer inspection it also appears that none of those servers respond to ICMP either. The traceroutes appear to never make it either...

II can't imagine that people are not aware of it. There's definitely some monitoring or integration platform screaming about it I guarantee it.

Hey Microsoft....Hit me up. 😎 I'd be happy to put our heads together and track it down.

🤙🏽📞

Dear all,

I have seen any number of comments stating that BSOD occurred or any other heavy system impact in this connection.

I strongly doubt that this (unfortunately still not solved issue by Microsoft) has any such relation/consequences.

I am pretty sure (it is so on all my machines) that after disabling automatic driver update via Control Panel -> System

-> Advanced system settings -> hardware tab -> Device installation settings - tick NO (your device ....)

you will not get any such errors in event viewer anymore. If you have any software which cares for latest driver updates

you are just fine.

Set it back to recommended form time to time to see whether Microsoft finally has solved the issue - why this has not

happened long ago after all these months, remains the secret of Microsoft!

Regards Viktor

I don't have any errors with the programs. There were 2 Other devices in the Device Manager. And after I updated the driver for the chipset, they disappeared. I don't know if this is related to the error 0x80070490. But it appears regularly in the Event View.

You can check out my created post.