свин (scif_yar) wrote in ru_sysadmins,
свин
scif_yar
ru_sysadmins

Win10 и январский апдейт

Оригинал взят у scif_yar в Win10 и январский апдейт
Накатил какой-то большой патч. После этого сломался Edge.
Вообще патч странный - после него остается windows.00 (перепроверю, но похоже).

Ощем проблема описана -
Late Friday, Dec. 4, Microsoft released its latest update for Windows 10 version 1511, an odd patch called KB 3122947. If you aren't actively blocking forced updates in Windows 10 and your machine could get KB 3122947 to install, you will find that your winver (in the Cortana search box, type "winver" and press Enter) comes up at 10586.17. Unfortunately, many people are seeing notifications that KB 3122947 failed to install with error 0x80070643.
http://www.infoworld.com/article/3012221/microsoft-windows/mysterious-new-windows-10-version-1511-patch-kb-3122947-fails-to-install-with-error-0x80070643.html

Но это ранние темы.
У меня же вылезло нечто типа
Windows update failed due to leftover profiles in registry from deleted user accounts. I deleted the profiles and the update installed "successfully" but Microsoft Edge fails to start with the following error in the event log:

Faulting application name: MicrosoftEdge.exe, version: 11.0.10240.16425, time stamp: 0x55bec30f
Faulting module name: eModel.dll, version: 11.0.10240.16425, time stamp: 0x55bebfb9
Exception code: 0xc0000409
Fault offset: 0x0000000000112b53
Faulting process id: 0x980
Faulting application start time: 0x01d0d9e8392c3c3f
Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe
Faulting module path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\eModel.dll
Report Id: a623621b-9d15-45a7-a0c2-3f8d2ac25c95
Faulting package full name: Microsoft.MicrosoftEdge_20.10240.16384.0_neutral__8wekyb3d8bbwe
Faulting package-relative application ID: MicrosoftEdge

Fault bucket 133174743127, type 5
Event Name: MoBEX
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.MicrosoftEdge_20.10240.16384.0_neutral__8wekyb3d8bbwe
P2: praid:MicrosoftEdge
P3: 11.0.10240.16425
P4: 55bec30f
P5: eModel.dll
P6: 11.0.10240.16425
P7: 55bebfb9
P8: 0000000000112b53
P9: c0000409
P10: 0000000000000007

Attached files:
C:\Users\klandymo\AppData\Local\Temp\WERCE29.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Micros_645dacfa21d01c2fe448990cea22ed8b1b4a0a9_fae04a53_15c4cfef

Analysis symbol:
Rechecking for solution: 0
Report Id: a623621b-9d15-45a7-a0c2-3f8d2ac25c95
Report Status: 0
Hashed bucket: 11584eb6ddfa4baa30dccc6ac39a57f4


https://social.technet.microsoft.com/Forums/en-US/0e84eb26-ebd1-440d-b04f-b53401fa6a6f/microsoft-edge-crashes-on-load-after-failed-windows-update?forum=win10itprogeneral

https://social.technet.microsoft.com/Forums/en-US/fd436515-6423-4015-9afe-d7e6034909ab/windows-10-threshold-2-edgesearch-issues-for-domain-joined-pcs

конечно, вот такой метод работает, но избранному капууут. Как и всем настройкам.
Step 1, go to C:\Users\[userprofile]\AppData\Local\Packages and delete the folder "Microsoft.MicrosoftEdge_8wekyb3d8bbwe"

and delete the folder "Microsoft.MicrosoftEdge_8wekyb3d8bbwe"

Step 2, open a Poweshell as Admin and run this command:

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" -Verbose}

This will reinstall Edge and keep it working until you reboot/logoff. It's not a pretty workaround.... I know.





Вопрос:
Я понимаю, тут у многих линукс, а у иных даже и Роса-М100500, но кто-то пробует 10-ку хотя бы и дома ? Как впечатление, нужен ли таз с проточной холодной водой - как было в 8-ке ?
Tags: поговорить, пятница
Subscribe
  • Post a new comment

    Error

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 19 comments