Kuskure 0x80070490: Cin hanci da rashawa a cikin sassan tsarin

El Kuskuren Windows 0x80070490 Ya zama ɗaya daga cikin waɗannan lambobin da ke bayyana a lokutan da ba su dace ba: lokacin shigar da sabuntawa, lokacin ƙoƙarin haɓakawa daga Gida zuwa Pro, lokacin ƙara asusun imel, ko ma lokacin kunna fasaloli kamar .NET Framework 3.5. Kodayake saƙon na iya yin sauti kamar ɓoye, a bayansa yawanci akwai matsaloli na musamman tare da direbobi, abubuwan da ke cikin Sabuntawar Windows, ko fayilolin sanyi da suka lalace.

A cikin wannan jagorar za ku sami cikakken bayani dalla-dalla Wannan jagorar ta ƙunshi duk sanannun dalilan kuskuren 0x80070490 da kuma hanyoyin da suka fi tasiri don gyara shi a cikin Windows 10, Windows 11, manhajar Mail da Calendar, Microsoft Store, Xbox, har ma a cikin yanayi mafi ci gaba tare da WSUS ko sabar. Za ku sami komai daga mafita masu sauƙi kamar amfani da na'urar warware matsala zuwa gyare-gyaren Registry na ci gaba, gyaran lalacewar tsarin, da sarrafa takamaiman direbobi.

Menene ainihin ma'anar kuskuren 0x80070490?

Lambar 0x80070490 yawanci yana nufin ERROR_NOT_FOUNDA wata ma'anar, Windows ba zai iya samun wani abu da yake buƙata don kammala aiki ba. A aikace, wannan yana bayyana kansa galibi a cikin manyan rukunoni uku na matsaloli:

A gefe guda, yana da alaƙa da kusanci da Sabuntawar Windows da shagon kayan aikin CBS (Sabis na Based Component), wanda shine tsarin ciki wanda ke sarrafa shigarwa, sabuntawa, da canje-canje da yawa na fasali. Idan akwai fayil ɗin da ya lalace, ko kuma an karya bayanin kula a cikin Registry, ko kuma direban da ya ɓace, CBS ya gaza kuma ya dawo da 0x80070490.

A gefe guda kuma, kuskuren yana bayyana lokacin da Manhajar Wasiku/Kalanda ko kuma asusun Microsoft ɗinka Ba za su iya samun damar saitunan da aka ajiye ba, izinin sirri, ko wasu bayanan mai amfani a cikin rajistar AppxAllUserStore. A waɗannan yanayi, za ku ga saƙon "ba mu sami saitunanku ba".

Bugu da ƙari, ana samun wannan lambar sau da yawa lokacin da Haɓakawa daga Windows Home zuwa Pro akan kayan aikin OEM (Asus, HP, Lenovo, Dell, da sauransu) saboda rikice-rikice tsakanin lasisin da aka saka a cikin BIOS da sabon bugu da kuke ƙoƙarin shigarwa ko kunnawa.

Mafi yawan dalilan fasaha na kuskuren 0x80070490

Akwai dalilai daban-daban a bayan lambar iri ɗaya 0x80070490Sanin su yana taimaka maka ka zaɓi mafita mai kyau kuma kada ka yi ƙoƙarin gwada abubuwa ba tare da tunani ba.

Ɗaya daga cikin shahararrun shine cin hanci da rashawa a cikin Ma'ajiyar Kayan Tsarin (CBS) ko kuma a cikin Sabis ɗin da ke Ba da Sabis na Abubuwan da Aka Haɗa. Nan ne fayilolin da suka lalace, shigarwar rajista marasa inganci, hanyoyin haɗin da suka karye a cikin tsarin, ko layukan aikin direba waɗanda ba su ɗora daidai ba suka shigo cikin aiki.

Wani dalili na gama gari shine Direbobi marasa cikawa ko marasa daidaiMisali, na'urori kamar "PCI Memory Controller" ko "SM Bus Controller" da ke bayyana a ƙarƙashin "Sauran na'urori" a cikin Device Manager suna nuna cewa ba a shigar da chipset ɗin daidai ba. Wannan na iya haifar da kurakurai a cikin DeviceSetupManager (event IDs 131 da 201) tare da saƙonni kamar "Kuskuren shirya metadata, sakamako=0x80070490".

Wadannan kuma suna da tasiri mai mahimmanci riga-kafi na ɓangare na uku da kuma firewalls masu ƙarfi wanda ke tace Windows Sabunta zirga-zirga ko toshe ayyukan kamar BITS, sabis ɗin ɓoye bayanai, ko wuauserv da kansa. A cikin waɗannan yanayi, kuskuren 0x80070490 yana bayyana ne kawai saboda ba a kammala sadarwa da sabar sabuntawa ba.

Bai kamata mu manta da hakan ba fayilolin sanyi marasa kyau, kamar fayil ɗin SetupConfig.ini mara komai ko wanda ya lalace a cikin shigarwar fasali ko sabbin bugu na Windows. Idan mai sakawa bai iya karanta saitin ba, zai dawo da 0x80070490 kuma ya daina aiki.

Kurakuran da suka shafi Sabuntawar Windows 0x80070490

Lokacin da ya bayyana yayin sabuntawaMafi yawan waɗanda suka fi yin hakan su ne sabis ɗin CBS, abubuwan ciki na Windows Update, ko kuma layin direban da ke kula da ayyukan shigarwa da cirewa.

A cikin waɗannan yanayi, Rikodin CBS.log da WindowsUpdate.log Su ne mabuɗi. Ana samun su a cikin C:\Windows\Logs\CBS\CBS.log Kuma a yanayin na biyu, ana samar da shi ta hanyar haɗa alamun Windows Update. Idan kuskuren ya bayyana, za ku ga layuka masu kama da:

An kasa karanta Identity don aikin direba, An kasa loda layin aikin direban da ya gaza o Doqi: An kasa loda layin ayyukan direbobi, duk tare da HRESULT = 0x80070490 (ERROR_NOT_FOUND). Wannan yana nuna cewa Windows ba zai iya gano asalin takamaiman aikin direba ba (sequenceID) ko kuma cewa wani abu a cikin jerin gwano ya ɓace.

Haka kuma abu ne da aka saba samu, a cikin sabunta fasali, shigarwar inda mai saka Setup360 ko WindowsUpdateBox.exe ya ƙare da Lambar dawo da tsari = 0x80070490, kuma yanayin shigarwa na ciki an sake saita shi zuwa "mara inganci".

Kurakuran gyara matsala da sabuntawa da ke jiran a yi da kuma layin direbobi ke haifarwa

A cikin tsarin da sabuntawa ke ci gaba da kasancewa a cikin yanayi "Ana jiran shigarwa"CBS na ƙoƙarin kammala jerin ayyukan mai sarrafawa wanda ya haɗa da abubuwa masu lamba (1, 2, da sauransu). Idan babban fayil ko maɓallin rajista da ke wakiltar aiki "1" ya lalace, tsarin zai jefa kuskure 0x80070490 saboda ba zai iya samunsa ba.

A cikin waɗannan yanayi, gyara na musamman Ya ƙunshi sarrafa hanyar:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Service\DriverOperations\1

Idan wannan ƙaramin maɓallin "1" ya lalace, zai iya faruwa cire shi a hankali (bayan an ajiye Registry ɗin a madadinsa) don Windows ta daina ƙoƙarin loda shi. Yana da mahimmanci a fitar da maɓallin kafin lokaci saboda dalilai na tsaro, musamman a yanayin sabar.

Na gaba, yana da kyau a tabbatar da cewa amintaccen sabis ɗin mai sakawa (Mai Shigarwa Mai AmintacceAn daidaita shi daidai. A gudanar da shi a cikin wani umarni mai girma:

tsarin trustinstaller na sc start=demand

Wannan yana tabbatar da cewa sabis ɗin da ke da alhakin shigar da kayan aikin Windows zai iya farawa akan buƙata ba tare da matsala ba. Da zarar an gama wannan, ana sake ƙoƙarin shigar da sabuntawa.

Sabunta fasalin da fayil ɗin SetupConfig.ini

Lokacin da kake ƙoƙarin shigar da Sabunta fasalin Windows 10 ko 11 (misali, haɓakawa daga wata siga zuwa wata a cikin tsarin ɗaya) ta hanyar Sabuntawar Windows ko Cibiyar Software (WSUS), 0x80070490 na iya bayyana a ƙarshen aikin, kamar yadda mai sakawa ke ƙoƙarin fara matakin Saita.

Rajistar WindowsUpdate.log tana nuna kira zuwa WindowsUpdateBox.exe ko kuma sassan kamar Setup360, waɗanda ke loda fayil ɗin tsari (SetupConfig.ini). Idan wannan fayil ɗin babu komai a ciki, ba a rubuta shi daidai ba, ko kuma ya ƙunshi sigogi marasa daidai, mai sakawa zai dawo da 0x80070490 kuma ya daina aiki.

Hanyar da ta fi dacewa zuwa fayil ɗin da ke da matsala ita ce:

C:\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini

Zaɓi ɗaya shine Share SetupConfig.ini kai tsaye don haka shigarwar ta ƙirƙiri sabuwa ta hanyar tsoho. Idan kana son ajiye wanda ke akwai, zaka iya gyara shi don tabbatar da cewa ya ƙunshi aƙalla layi ɗaya mai daidaito, misali:

Nuna OOBE=Babu

Da fayil ɗin daidaitawa daidai ko kuma an sake sabunta shi, shigarwar sabunta fasalin yawanci yana kammala ba tare da lambar 0x80070490 ta sake bayyana ba.

Kurakurai 0x80070490 a cikin sabuntawar tarin bayanai da lalacewar tsarin

Wani bambancin da aka saba gani yana faruwa tare da sabuntawa na tarawa na wata-watawanda wani lokacin yana dawo da 0x80070490 tare da ƙarin lambobi kamar 0x8e5e03fa. A cikin Windows Event Log za ku ga saƙonni inda takamaiman fakiti (misali KB5004122 ko KB5004298) ke ƙoƙarin canzawa zuwa yanayin "An shigar" kuma sun gaza tare da wannan lambar matsayi.

Waɗannan gazawar yawanci suna da alaƙa da cin hanci da rashawa na fayilolin tsarin ko kuma a cikin tsarin ma'ajiyar kayan aiki, don haka gyaran da aka saba yi ya ƙunshi kayan aikin SFC da DISM da aka haɗa.

Daga umarnin umarni tare da gata na mai gudanarwa, ana ba da shawarar gudanar da waɗannan umarni a cikin wannan tsari:

DISM / Kan layi /Tsabtace-Hoto /Mayar da Lafiya
SFC/Scannow

DISM yana duba kuma yana dawo da hoton Windows ta amfani da fayilolin tunani, yayin da Mai Duba Fayil na Tsarin ke gyara fayilolin da suka lalace. Idan DISM ta gano kuma ta gyara ɓarna a cikin shagon CBS, SFC za ta sami damar yin nasara mafi girma.

Bayan gyara, kyakkyawan ra'ayi ne Sake saita wasu sassan Sabuntawar Windows, musamman babban fayil ɗin Catroot2 da rarraba software:

tasha ta yanar gizo cryptsvc
cd %systemroot%\system32
xcopy catroot2 catroot2.old / s
del %systemroot%\system32\catroot2\* /q
fara yanar gizo cryptsvc

Kuma ga Fayil ɗin Rarraba Software:

tasha ta yanar gizo wuauserv
cd %tsarin tsarin%
ren SoftwareDistribution SoftwareDistribution.old
fara yanar gizo wuauserv

Da zarar an kammala waɗannan matakan, Gwada sake shigar da facin. Ga abin da zai faru a gaba. Idan cin hancin ya kasance ƙarami ko kuma an iyakance shi ga sabunta fayiloli, 0x80070490 yawanci yakan ɓace.

Fayilolin direba da suka ɓace da kuskuren 0x80070490

A cikin yanayi mafi ci gaba, kamar sabar ko kwamfutoci masu takamaiman ayyuka, kuskuren 0x80070490 na iya kasancewa saboda takamaiman direbobi da suka ɓace daga DriverStoreMisalin da aka rubuta shi ne na na'urar sarrafawa wvms_pp.inf, wanda wasu sassan kama-da-wane da gudanarwa ke amfani da su.

Idan CBS.log ya ƙunshi saƙonni masu zuwa Shtd: An kasa aiwatar da layin ayyukan direbobi marasa mahimmanci Tare da HRESULT = 0x80070490, kuma an ambaci wannan mai sarrafawa, mafita ta ƙunshi sake gina kasancewarsa a cikin tsarin.

Tsarin da aka saba amfani da shi ya ƙunshi ƙirƙirar fayil da hannu kamar haka:

C:\Windows\System32\DriverStore\FileRepository\wvms_pp.inf_amd64_81d18de8de8dedd4cc4

Na gaba, duk .inf da fayilolin da suka shafi ana kwafi su daga hanyar WinSxS mai dacewa, wani abu kamar haka:

C:\Windows\WinSxS\amd64_wvms_pp.inf_31bf3856ad364e35_6.2.9200.22376_none_bc457897943a83fe

Domin kammala gyaran, ana loda ƙaramin tire na direban cikin Rijista kuma ana duba shigarwar. HKEY_LOCAL_MACHINE \DriverDatabase\DriverInfFiles\wvms_pp.inf Nuna daidai ga waɗannan fayilolin. Wannan zai ba da damar sarrafa jerin ayyukan mai sarrafawa ba tare da jefa 0x80070490 ba.

Amfani da Mai Gyaran Matsalolin Sabuntawar Windows

Kafin yin rikici da Registry ko sake suna manyan fayilolin tsarin, yana da kyau a yi gwada abin da Windows kanta ke bayarwaMai warware matsalar Sabuntawar Windows yana warware mafi sauƙin kurakurai 0x80070490 ba tare da buƙatar kowane umarni ba.

A cikin Windows 10 da 11, ana iya samunsa daga Gida > Saituna > Sabuntawa & Tsaro > Shirya matsala, sannan a shiga cikin "Ƙarin Masu Gyaran Matsaloli" ko "Sauran Masu Gyaran Matsaloli" don gudanar da Mai Gyaran Matsalolin Sabunta Windows.

Wannan kayan aikin yana nazarin ayyukan da abin ya shafa ta atomatik, izinin babban fayil ɗin maɓalli, jerin sabuntawa, da kuma matsayin mai saka BITS da Windows module, yana gyara matsaloli da yawa na yau da kullun. Wannan yana da mahimmanci. Kada a kashe kayan aikin yayin da yake aiki, domin yana iya ɗaukar lokaci.

Idan a ƙarshe yana nuna cewa an gyara kurakurai, Sake kunna PC ɗinka kuma danna "Duba don sabuntawa". Wannan shine matakin da aka ba da shawarar ɗauka. Idan kuskuren 0x80070490 ya faru ne saboda ƙaramin rikici, da wuya ya sake faruwa.

Idan wannan mafita bai isa ba, za ka iya komawa Gyaran TagogiKayan aiki na ɓangare na uku yana sarrafa yawancin matakan da aka bayyana (sake kunna ayyuka, sake saita izini, gyara abubuwan sabuntawa). Gudanar da saitin "Sabuntawa na Windows" yana sake saita saitunan ciki da yawa waɗanda galibi ke bayan matsalar.

Kashe software na riga-kafi na ɓangare na uku kuma duba manyan ayyuka

Wani batu da ake yawan mantawa da shi shine tasirin riga-kafi na ɓangare na uku kuma daga firewalls da aka haɗa cikin suites na tsaro. Waɗannan shirye-shiryen, ta hanyar sa ido kan zirga-zirgar ababen hawa da kuma gyara takaddun shaida, na iya tsoma baki ga haɗin da Windows Update ke buƙata da sabar Microsoft.

Idan kwamfutarka tana da wani shirin riga-kafi da aka sanya banda wanda aka sanya Mai Tsaron WindowsYa cancanci hakan: kariyar lokaci-lokaci, firewall, da duk wani tsarin duba yanar gizo. Bayan kashe shi, sake kunna kwamfutar kuma sake gwada sabuntawa.

A cikin yanayin da ake amfani da Windows Defender kawai, wani lokacin yana da kyau a duba cewa babu wani abu da ya faru. kariyar lokaci-lokaci Ba zai bar tsarin a cikin wani yanayi na tsaka-tsaki ba, kuma ba a toshe ayyukan sabuntawa ba bisa ga kuskure.

Bugu da ƙari, yana da kyau a tabbatar cewa ayyukan da ake buƙata don Sabuntawar Windows suna aiki. Don yin wannan, danna Run (Win + R). ayyuka.msc kuma ana duba yanayin waɗannan masu zuwa:

Sabuntawar Windows (wuauserv), Sabis na Canja wurin Fasaha na Baya (BITS), Sabis na rubutun sirri, Mai Shigar da Windows (MSI).

Idan ana tsare da wani ba tare da wani dalili ba, gwada fara shi da hannu Wannan ita ce gwajin nan take. Idan bai yi aiki ba, kuskuren na iya kasancewa a cikin sabis ɗin da kansa, wani abu da DISM/SFC ko mai gyara matsalar Windows Repair yawanci zai iya gyarawa.

Sake saita abubuwan Sabuntawar Windows da hannu

Idan mai warware matsalar ko umarni na asali ba su magance matsalar ba, mataki na gaba mai ma'ana shine sake saita abubuwan Sabuntawar Windows da hannuWannan ya ƙunshi dakatar da ayyuka, sake suna manyan fayiloli na ciki, da kuma sake fara komai daga farko.

Tare da umarnin umarni a matsayin mai gudanarwa, ana amfani da toshe na farko na umarni don dakatar da ayyukan da ke cikin saukewa da shigarwa:

tasha ta yanar gizo wuauserv
tasha ta yanar gizo cryptSvc
net tasha ragowa
net tasha msiserver

Tare da dakatar da ayyukan, sake suna ga manyan fayilolin da ke adana su sabunta ma'ajiyar bayanai don tilasta sake farfaɗowa:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old

Ana sake sabunta waɗannan manyan fayiloli ta atomatik lokacin da aka sake kunna ayyuka, don haka sake sunansu yana tilasta wa Windows ƙirƙirar sabon "shagon sabuntawa".

A ƙarshe, an sake fara ayyuka:

fara yanar gizo wuauserv
fara net cryptSvc
net start bits
net fara msiserver

Bayan sake kunna kwamfutar, Sabuntawar Windows ta sake buɗewa kuma Nemi sabuntawarWannan nau'in sake saitawa da hannu yawanci yana ceton rai ne lokacin da 0x80070490 ya faru ne saboda cache mara kyau ko tarihin sabuntawa mara kyau.

Mayar da tsarin zuwa wurin da ya gabata

Idan kuskuren 0x80070490 ya fara bayyana jim kaɗan bayan wani sabuntawa ko shigar da wani shiri mai karo da juna, zaɓi mai kyau shine komawa zuwa wurin maidowa a baya, inda tsarin ya kasance mai karko.

Don yin wannan, danna Win + R kuma gudanar da shi rstruiWannan yana buɗe maye Maido da Tsarin. Zaɓi "Nuna ƙarin wuraren dawo da" kuma zaɓi ɗaya daga ciki kafin kuskuren ya fara faruwa ko kuma kafin wani takamaiman aikace-aikacen ya fara aiki ba daidai ba.

Tsarin zai sake kunna kwamfutar kuma ya dawo da Windows zuwa matsayinta tun daga wannan ranar, gami da fayilolin tsarin, saituna, da kuma Rijistar. Yawancin lokaci ana adana takardu na sirri, amma yi madadin kawai idan akwai Aiki ne mai kyau.

Da zarar an dawo da shi, Gwada Sabuntawar Windows kuma ko aikin da ya bayar da kuskuren 0x80070490 Wannan shine binciken ƙarshe. Idan gazawar ta shafi canje-canje na baya-bayan nan, dawo da tsarin yawanci mataki ne mai tasiri kuma ba mai cutarwa ba.

Kurakurai 0x80070490 lokacin haɓakawa daga Windows Home zuwa Pro akan kwamfutocin OEM

A cikin kwamfutocin tafi-da-gidanka da kwamfutocin tebur daga masana'antun kamar Asus, HP, Lenovo, Dell, Acer, da sauransu, abu ne da aka saba samu Kuskure 0x80070490 lokacin haɓakawa daga Gida zuwa Prohar ma da amfani da lasisin da aka saya daga Shagon Microsoft ko maɓallan dillalai masu inganci don bugu na Pro.

Tushen matsalar yawanci yana cikin Lasisin OEM da aka saka a cikin BIOS/UEFITsarin koyaushe yana "ganin" maɓallin Gida kuma, lokacin da kuka yi ƙoƙarin canzawa zuwa Pro, yana haifar da rikici tsakanin bugu na yanzu da sabbin bugu, yana haifar da lambar kuskure.

Akwai hanyoyin da suka dace da zamani cire maɓallin OEM daga ISO ɗin shigarwa kuma a yi shigarwa mai tsafta ta musamman, amma waɗannan matakai ne masu rikitarwa kuma sun haɗa da tsara kwamfutar, don haka Ba a ba da shawarar ga kowa da kowa ba.

Hanya mafi araha don rage waɗannan rikice-rikice ita ce a tabbatar da cewa tsarin yana da cikakken tsari kafin a yi ƙoƙarin haɓaka bugu. Don yin wannan, gudanar da umarni mai zuwa daga na'urar gudanarwa:

sfc /scannow
DISM / Kan layi / Hoton Tsaftacewa /StartComponentTsaftacewa
DISM / Kan layi /Tsabtace-Hoto /Mayar da Lafiya

Da zarar an gama gyara. gwada haɓakawa zuwa Pro kuma Mataki na gaba shine ko dai daga Shagon Microsoft (idan kuna son canza bugu kawai ba tare da kunna ba tukuna) ko kuma daga Saituna > Tsarin > Kunnawa ta hanyar shigar da ingantaccen maɓallin Pro (Retail, OEM, VLSC, da sauransu).

Kuskure 0x80070490 lokacin kunna .NET Framework 3.5 tare da DISM

Wani yanayi da ake gani a Windows 11 shine gazawar yin amfani da tsarin aiki Kunna fasalin .NET Framework 3.5 ta amfani da DISM, duka tare da fayilolin gida da kuma kai tsaye daga Sabuntawar Windows. Kodayake sandar ci gaba ta kai 100%, tsarin ya ƙare da "Kuskure: 1168 - Ba a samo abu ba", wanda a ciki ya fassara zuwa 0x80070490.

Umarnin da aka saba amfani da shi wani abu ne kamar haka:

DISM / Kan layi / Kunna-Fasalin /Sunan Siffa:NetFx3 /Duk /LimitAccess /Source:E:\sources\sxs

Inda E: shine harafin tuƙi na ISO na Windows. Idan hanyar zuwa tushe/sxs Idan abubuwan da ke cikin ISO na sigar iri ɗaya da aka gina da wanda aka shigar ba su dace ba, DISM ba zai iya nemo fakitin da ake buƙata ba kuma ya dawo da kuskuren.

Don magance matsalar, yana da mahimmanci a yi amfani da shi ISO wanda ya dace da sigar hoton Duba sigar DISM (misali, 10.0.22621.2506) kuma tabbatar da cewa babban fayil ɗin tushen\sxs yana ɗauke da fakitin NetFx3. A kan wasu tsoffin kafofin shigarwa, waɗannan fayilolin ba za su kasance ba.

Idan tushen gida bai aiki ba, zaku iya gwada gudanar da umarni ɗaya amma ba tare da /LimitAccess ba don ba da damar DISM ta cire daga rumbun adana bayanai na Microsoft, muddin kwamfutar tana da haɗin kai kuma babu toshewar wakili ko firewall.

Kurakurai na DeviceSetupManager, metadata, da direbobin chipset

A cikin Mai Duba Taro, a ƙarƙashin asalin Na'urarSaitawaManajan Na'uraKurakurai tare da ID 131 ko 201 na iya bayyana, gami da sakamakon 0x80070490 ko lambobi kamar 0x80072EFE. Saƙonni kamar "Kuskuren shirya metadata, sakamako=0x80070490" suna nuna matsalolin dawo da bayanan na'ura daga ayyukan metadata na Windows.

A wani yanayi na yau da kullun tare da motherboard na ASUS PRIME H310M-K R2.0 da Windows 10 Pro 22H2, bayan sake shigar da tsarin, abubuwan "PCI Memory Controller" da "SM Bus Controller" sun bayyana a cikin "Sauran na'urori" na Device Manager, ban da gumakan agogo a cikin "Na'urori da Firintocin".

Waɗannan alamomin suna nuna kai tsaye ga ba a shigar da direbobin chipset baTa hanyar saukarwa da shigar da fakitin "Intel Chipset Driver" mai dacewa don motherboard daga gidan yanar gizon ASUS na hukuma, waɗannan na'urorin sun ɓace daga jerin na'urorin da ba a sani ba kuma kurakuran DeviceSetupManager sun daina faruwa akai-akai.

A irin waɗannan yanayi, sabunta direban chipset shawara ce mai kyau, domin tana ba da damar daidai ganewar na'urorin allonDangane da "Intel Management Engine Interface", Windows sau da yawa yana shigar da direba na gama gari ta hanyar Sabuntawar Windows, don haka ba koyaushe dole ne a shigar da wanda ke gidan yanar gizon masana'anta ba idan komai yana aiki daidai.

Dangane da wasu direbobi (LAN, Realtek audio, VGA, SATA), ana ba da shawarar shigar da su daga gidan yanar gizon masana'anta idan kun ga na'urori ba tare da direbobi ba ko kuma idan kuna amfani da fasaloli na ci gaba. Duk da cewa ba yawanci su ne sanadin kuskuren 0x80070490 kai tsaye ba, samun chipset da direbobin tushe na zamani yana rage haɗarin wannan nau'in kuskuren sosai.

Alaƙa da BIOS da sabuntawa na zaɓi

Mutane da yawa suna mamaki ko BIOS ɗin da ya tsufaMisali, samun sigar 1005 lokacin da masana'anta ke kan sigar 2208 na iya zama tushen kuskuren 0x80070490. A mafi yawan lokuta a gida, amsar ita ce BIOS ba ta da tasiri sosai kan wannan nau'in kuskuren; tabbas, yana da kyau a... Gano ko matsalar ta shafi hardware ne ko software..

Sabunta BIOS yana da haɗari, don haka Ba shine matakin farko da za a yi la'akari da shi baYana da kyau a tabbatar da cewa chipset, LAN, masu sarrafa sauti da zane-zane An sabunta su kuma an shigar da sabbin direbobin Sabuntawar Windows cikin hikima, ana zaɓar waɗanda ake buƙata kawai.

A cikin sashen na "Haɓakawa na zaɓi" A cikin Windows 10/11, direbobin Intel da yawa waɗanda ke da tsoffin kwanan wata (kamar 2016 ko ma 1968, wanda alama ce ta musamman) wani lokacin suna bayyana. Idan kun shigar da kunshin chipset na hukuma kuma wasu daga cikin waɗannan direbobin sun ɓace daga jerin, alama ce mai kyau: yana nufin masana'anta yanzu suna samar da sabbin sigogi, kuma ba kwa buƙatar dogaro sosai da direbobin gabaɗaya daga Sabuntawar Windows.

Dangane da canza sabar lokacin Intanet, kashe saukar da bayanan na'urori ta atomatik, ko gyara maɓallin DeviceMetadataServiceURL a cikin Registry, waɗannan suna da ma'ana ne kawai a cikin takamaiman yanayi inda aka san matsalar tana da alaƙa da saukar da bayanan metadata. A mafi yawan lokuta lambar kuskure 0x80070490, Ba lallai ba ne a daidaita waɗannan sigogi.

Kuskuren 0x80070490 a cikin manhajar Mail da Calendar

Lambar 0x80070490 kuma tana bayyana tana da alaƙa da Manhajar Wasiku ta Windows 10/11Wannan ya zama ruwan dare musamman lokacin ƙoƙarin ƙara asusun imel na biyu, ko Outlook ne, Gmail, ko wani mai bada sabis. Saƙon yawanci yana nuna cewa ba a sami saitin ba ko kuma aikin ya gaza tare da lambar da aka ƙayyade.

A cikin gida, wannan yawanci yana faruwa ne saboda shigarwar da aka lalata a cikin shagon AppxAllUserStore, saboda rashin daidaitaccen tsarin izinin sirri ko kuma shigar da manhajar Mail da Calendar da kanta ba daidai ba.

Mataki na farko mai kyau shine a sake duba shi saitunan sirri: Saituna > Sirri > Imel da Kalanda, kuma tabbatar da cewa an ba wa manhajoji damar shiga imel da kalanda, kuma manhajar Mail da Kalanda tana da izini bayyananne.

Bayan haka, yana da amfani sosai Sabunta manhajar daga Shagon MicrosoftA Shago, je zuwa "Laburare" > "Sami sabuntawa" kuma yi amfani da duk wani sabuntawar Wasiku da Kalanda da ke jiran a yi. Sau da yawa, kuskuren yana ɓacewa bayan sabunta manhajar.

Idan hakan bai isa ba, za ka iya zuwa Saituna > Manhajoji > Wasiku da Kalanda > Zaɓuɓɓuka na Ci gaba kuma yi amfani da maɓallin don Dawo daWannan yana share bayanan gida na manhajar, wanda daga baya aka sake tsara shi daga farko. A cikin mawuyacin hali, ana iya cire shi ta amfani da PowerShell (Get-AppxPackage Microsoft.Windowscommunicationsapps | Remove-AppxPackage) sannan a sake shigar da shi daga Shagon.

Idan cin hanci ya shiga cikin rajistar AppxAllUserStore, mafita mai inganci ta ƙunshi cire maɓallan S-1-5-21-… A ƙarƙashin HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore, nemo duk wani ID na mai amfani wanda babu shi, sannan a sake kunna shi. Wannan yana cire tsoffin ma'ajiyar mai amfani waɗanda ka iya haifar da matsaloli.

Amfani da SFC da DISM don matsalolin wasiku da daidaitawa

Ko da kuskuren 0x80070490 ya bayyana a cikin manhajar Mail ko saitunan asusu, yana da kyau a gudanar da Scan na SFCDaga umarnin umarni a matsayin mai gudanarwa, ƙaddamar:

sfc /scannow

Mai duba yana duba duk fayilolin tsarin da aka kare kuma Maye gurbin waɗanda suka lalace da kwafi na daidaiTsarin zai iya ɗaukar tsakanin mintuna 15 zuwa 20, kuma idan ya gano matsaloli a cikin rumbun ajiyar bayanai na CBS, zai nuna hakan a ƙarshe.

Idan an bayar da rahoton cin hanci da rashawa a CBS, yana da kyau a ci gaba da bin diddigin DISM:

DISM / Kan layi / Hoton Tsaftacewa /Lafiya ta Duba
DISM / Kan layi /Tsabtace-Hoto /Mayar da Lafiya

A ƙarshe, ana ba da shawarar Sake kunna kuma gwada sake ƙara asusun. a cikin manhajar Mail ko kuma maimaita aikin daidaitawa wanda ke haifar da kuskuren. SFC da DISM, idan aka yi aiki daidai, suna gyara yawancin matsalolin tsarin da ke haifar da lambar kuskure 0x80070490, ba tare da la'akari da inda suka faru a cikin Windows ba.

Kodayake lambar 0x80070490 na iya zama abin tsoro, kusan koyaushe yana samo asali ne daga sanannun dalilai: Sabis na Sabunta Windows da aka lalata, layin direbobi da suka lalace, bayanan martaba na mai amfani masu matsala, ko aikace-aikacen UWP da aka shigar ba daidai baTa hanyar haɗa kayan aikin da aka gina a ciki (mai warware matsala, SFC, DISM, dawo da tsarin), sake shigar da direbobi masu mahimmanci (chipset, direbobin tushe na masana'anta), da kuma, idan ya cancanta, wasu gyare-gyare na gaba zuwa manyan fayilolin Rijista da tsarin, yana yiwuwa a dawo da kwanciyar hankali ga kwamfutar ba tare da yin tsari ko farawa daga farko ba.