KB5005033 August 2021 cumulative update

CrazyKats 19,595 Reputation points Volunteer Moderator
2021-08-10T18:15:15+00:00
Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

108 answers

Sort by: Newest
  1. Anonymous
    2021-08-14T14:03:05+00:00

    I am not an expert at this but since it says you must uninstall both at the same time, I might think you had to use the .cab file to do so. On my system the .cab file is in the SoftwareDistribution folder. If you cannot find it then download it and put it where you want.

    If you have already uninstalled the update then it may not work if you can't uninstall both at the same time, so you may even have to reinstall the update and try again with the .cab file. Keep in mind, an update may change how your system behaves not just due to some error with the update but possibly just some settings change during that update.

    On my system it would look like this.. Yours may be different so this is just an example. Double check the full command, do not copy and paste..

    DISM /online /Remove-Package /PackagePath:C:\Windows\SoftwareDistribution\Download\406e2365941935ae889f311039fc7ea6 \Windows10.0-KB5005033-x64.cab

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-08-14T13:13:31+00:00

    Hi Omar_101, how did you uninstall this update? I've been having trouble uninstalling it.

    Thanks.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-08-14T06:11:30+00:00

    thank you

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-08-14T02:23:51+00:00

    Ugh, I totally misread that section thinking that would remove only the LCU and not the SSU.

    However, I tried running the DISM /online /Remove-Package as instructed, but I get an error saying the Permanent package cannot be uninstalled in the logs. I'm using the PackageName options as I don't know the path to the CAB file. Would that make a difference? Is there a CAB file somewhere?

    Thank you for the help.

    CPackageManagerCLIHandler::ExecuteCmdLine

    2021-08-13 22:03:12, Info DISM DISM Package Manager: PID=9776 TID=9452 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine

    2021-08-13 22:03:12, Info DISM DISM Package Manager: PID=9776 TID=9452 Encountered the option "packagename" with value "Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1161.1.1" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine

    2021-08-13 22:03:12, Info DISM DISM Package Manager: PID=9776 TID=9452 Package Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1161.1.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping

    2021-08-13 22:03:12, Info DISM DISM Package Manager: PID=9776 TID=9452 Initiating Changes on Package with values: 5, 0 - CDISMPackage::Internal_ChangePackageState

    2021-08-13 22:03:12, Error DISM DISM Package Manager: PID=9776 TID=9452 Failed initiating changes - CDISMPackage::Internal_ChangePackageState(hr:0x800f0825)

    2021-08-13 22:03:12, Error DISM DISM Package Manager: PID=9776 TID=9452 Failed to Remove the Package. - CDISMPackage::Remove(hr:0x800f0825)

    2021-08-13 22:03:12, Error DISM DISM Package Manager: PID=9776 TID=9452 Permanent package cannot be uninstalled. - GetCbsErrorMsg

    2021-08-13 22:03:12, Error DISM DISM Package Manager: PID=9776 TID=9452 Failed while processing command remove-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0825)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2021-08-13T23:17:02+00:00

    Single click on QUICK LAUNCH TOOLBAR stopped working after 2021-07 & or 2021-08 updates.

    Hope this gets fixed!

    Was this answer helpful?

    0 comments No comments