20,218 questions
Issue was that I had a custom action script which had a spelling mistake. After correcting that its working fine
Feature Upgrade from Windows 10 1809 to 1909 is failing 0x80240022
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 4%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
lalajee
1,821
Reputation points
Hi, I'm try to upgrade Windows 10 1809 to 1909 but Its keep failing with error code 0x80240022
WUAHandler.log
Installation job encountered some failures. Error = 0x80240022. Commit Result = 0x00000001
I have try following things.
- Remove Windows_BT folder and SoftwareDistribution
- Machine Reboot
- Check all compatdata xml file cant see any block
- Checked Setupact file cant see any issue
Windows for business | Windows Server | User experience | Other
Windows for business | Windows Client for IT Pros | User experience | Other
2 answers
Sort by: Most helpful
-
lalajee 1,821 Reputation points
2020-09-22T15:47:42.92+00:00 -
Fiona Yan-MSFT 2,311 Reputation points2020-09-23T02:42:34.627+00:00 Thanks for your feedback and I'm glad the problem is solved now.
If you have any questions in future, we warmly welcome you to post in this forum again.Have a nice day!
Sign in to comment -
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 50%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENM%3C/text%3E%3C/svg%3E)
Nico Mueller 1 Reputation point2020-09-22T11:12:13.727+00:00 Hello!
Try looking at the windowsupdate.log (usually in C:\Windows) for further information.
Known fixes for this issue are initiating the Software Update Scan process or stoppng the WUA service, renaming the Software Distribution Folder and re-starting the WUA services.
While these are not guaranteed to solve your issue, it could be a nudge in the right direction!Regards,