none
Feature update to 1607 fails with 0x80240031 "the file is in the wrong format"

    Question

  • I'm kinda stumped on this one. This is not the 'hash' error that gets resolved by those required wsus updates/cleanup - I actually have had several clients successfully apply this update, but I have many more that fail with the given error. I found advice that maybe resetting wupdate...

    PS C:\windows> stop-service bits
    PS C:\windows> stop-service wuauserv
    PS C:\windows> stop-service appidsvc
    PS C:\windows> stop-service cryptsvc

    PS C:\windows> rename-item .\SoftwareDistribution SoftwareDistribution.bak
    PS C:\windows> rename-item .\system32\catroot2\catroot2.bak

    PS C:\windows> start-service bits
    PS C:\windows> start-service wuauserv
    PS C:\windows> start-service appidsvc
    PS C:\windows> start-service cryptsvc

    <after system reboot, still can't apply the update>

    dism.exe /online /cleanup-image /restorehealth

    <restart, still can't apply>

    ...and now I'm kind of stumped. On one system, I was able to manually apply the update from Windows Update, but I've no idea why that worked. Like I said, I do have many clients that successfully run this update from my Config Mgr / WSUS, so I don't think there's a server-side problem going on. WSUS has all the related hotfixes and is in a good way, and all config mgr clients are 5.00.8458.1520 which includes the hotfix for the erroneous 'hash error'.


    born to learn!


    • Edited by AJM Admin Wednesday, March 8, 2017 2:39 PM
    Wednesday, March 8, 2017 2:37 PM

All replies