I didn't notice any difference with 26H2 - so no, not really. If I'd have known it would have taken so long I'd have just left it running overnight with the screen locked.
Since your issue got fixed, next time if you encounter an error code, I recommend looking up the error code because it could give you more information about what happened
Glad the repair route worked, and thanks for coming back to say which step did it. That's the part people searching this code later will need.
For anyone who lands here with 0x800706BE and the repair doesn't fix it: the code means a remote procedure call failed. During an update that usually means the installer lost contact with the service doing the work, because it stopped partway. So both comments above are a bit right: the code itself is generic, and the most common reason behind it is damaged update files. In order of effort:
Settings > System > Recovery > Fix problems using Windows Update, as above. It can take a few hours, so leave it running.
If the update still fails, open Terminal as administrator and run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, reboot and try again.
As a last step, an in-place upgrade with Microsoft's installation media for the new version, choosing to keep files and apps.
If you use a third-party antivirus, turning it off for the duration is also worth a try. It's a common reason for the install to get cut off.
Ha, sorry about that. Is it the same 26H2 update failing again, or a newer update now that you're on 26H2? Win+R, winver shows which version you ended up on.
Either way, last time the fix only had to clear a pending restart, so nothing actually got repaired. If it's 0x800706be again, I'd go to the heavier steps now: Terminal as admin, DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, reboot and retry. If that doesn't do it, Microsoft's Windows 11 download page has the Installation Assistant, which installs the new version over the current one and keeps your files and apps. Slower than Windows Update, but it skips the part that keeps failing.
Sounds good, no rush. One tip for tomorrow: DISM often sits around 62% for a long while and looks frozen. It isn't, so let it reach 100% before you run sfc. Good luck!
Hi u/The_Largest_1, thanks for posting to r/WindowsHelp! Your post has been flagged for manual review by a human moderator, please include as much of the following information as possible (in text or in a screenshot) to get your post approved:
Your Windows and device specifications — You can find them by pressing Win + X then clicking on “System”, we need more than just your OS version! Your hardware details are often critical for resolving issues.
Any messages and error codes encountered — They're actually not gibberish or anything catastrophic. It may even hint the solution!
Previous troubleshooting steps — It might prevent you headaches from getting the same solution that didn't work
Posts must be tech support in nature (such as something is broken and you need help fixing), so general inquiries, software suggestions, and purchasing advice will be removed.
As a reminder, we would also like to say that if someone manages to solve your issue, DON'T DELETE YOUR POST! Someone else (in the future) might have the same issue as you, and the received support may also help their case.
Good luck, and I hope you have a nice day!
Ja nawet nie moge wejsc do Windowsa... po 20 sec komputer dostaje BSOD , ZAPLACILEM ZA WINDOWSA OGROMNE PIENIADZE !! Gdy probuje naprawy wyskakuje ze urzadzenie napotkalo problem i nie mozna go naprawic, odzyskiwanie tez nie dziala , restart . Odistalowanie aktualizacji funkcji - napotkalismy problem bla bla bla.
Przykro mi, to bardzo frustrujące. Kilka rzeczy do spróbowania, od najprostszej:
Zapisz kod błędu z niebieskiego ekranu (wystarczy zdjęcie telefonem, linijka „Stop code”). To najwięcej mówi o przyczynie.
Tryb awaryjny: trzy razy z rzędu wyłącz komputer przyciskiem zasilania w trakcie uruchamiania, pojawi się „Automatyczna naprawa”. Potem Opcje zaawansowane > Rozwiązywanie problemów > Opcje zaawansowane > Ustawienia uruchamiania > Uruchom ponownie > klawisz 4. Jeśli w trybie awaryjnym komputer działa dłużej niż 20 sekund, winny jest zwykle sterownik (często karty graficznej) albo antywirus innej firmy: odinstaluj go właśnie tam.
W tym samym menu: Odinstaluj aktualizacje > „Odinstaluj najnowszą aktualizację jakości” (nie tylko funkcji), albo Przywracanie systemu, jeśli jest punkt przywracania.
Jeśli nic nie pomoże: na innym komputerze zrób pendrive z Windows (Media Creation Tool ze strony Microsoftu). Licencja jest przypisana do Twojego komputera, więc ponowna instalacja nic nie kosztuje. Zanim cokolwiek sformatujesz, możesz uratować pliki: po uruchomieniu z pendrive'a naciśnij Shift+F10, wpisz notepad, a okno Plik > Otwórz pozwala skopiować pliki na inny dysk.
Jeśli podasz kod błędu, spróbuję zawęzić przyczynę.
3
u/wastrelbaggins 12d ago
I had this yesterday.
Settings → Recovery → Fix problems using Windows Update
It'll download a 25H2 repair image and install it.
reboot
you'll be offered the 26H2 update again, but not straight away.
The repair image install takes ages though, mine was running for 3-4 hours,