The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 4,224 other subscribers

Archive for March 20th, 2023

De akoestiek is in veel Amsterdamse horeca beroerd – en dat kost klanten: ‘Als ik moet schreeuwen, haak ik af’

Posted by jpluimers on 2023/03/20

Herkenbaar. Hoe geweldig het eten en bediening ook: herrie in de horeca sluit mensen met een beperking uit.

[Archive] De akoestiek is in veel Amsterdamse horeca beroerd – en dat kost klanten: ‘Als ik moet schreeuwen, haak ik af’

–jeroen

Posted in About, Personal | Leave a Comment »

Windows: investigating error code 0x80073701 and 0x800f081f while updating; some DISM and CBS log things to search for

Posted by jpluimers on 2023/03/20

A while ago when applying KB5008212* through Windows Update, I got errors. It was odd, as until now, all other upgrades had worked fine.

Often Windows update errors are because of lack of disk space (I try maintain 10 gigabytes or more free space on virtual machines, but that sometimes fails because some software – despite user files being on a different drive – sometimes insists on filling the system drive).

This time, Windows Update would show 0x80073701, of course right after reaching 100%, but actually it was a 0x800f081f  in disguise.

My usual modus operandi didn’t solve it (with a retry after every step):

  1. Reboot
  2. Cleanup of the system drive using built-in CleanMgr.exe (Disk cleanup)
  3. Scan all corrupted system files and replace them from cache: SFC /ScanNow (System File Checker)
  4. Cleanup and repair the Windows image using DISM /Online /Cleanup-image /Restorehealth (Deployment Image Servicing and Management)

All failed, but in the last step, DISM would consistently show error 0x800f081f.

Even a local DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\Windows\WinSxS /LimitAccess would fail.

Each DISM run will actually log in two log files, and this is the trick to figure out what the next step would be.

Examples from my case:

Read the rest of this entry »

Posted in Power User, Windows, Windows 10 | Leave a Comment »

 
%d bloggers like this: