2 Intern
•
28 Posts
0
549
July 21st, 2024 04:16
m16 R2, reboot, Windows says it's installing updates, but then "We couldn't complete the features."
New Alienware m16 R2, Windows is fully up to date, so is SupportAssist. There are no updates at all to install. And yet, several times a day, if I go to reboot the system, it shows me that it's trying to install updates. It immediately starts by saying it's 15% done, and that number slowly increases to 29%, at which point it actually reboots. Then it tells me it's finishing up installing updates, and then quickly displays the message:
"We couldn't complete the features.
No need to worry--undoing changes.
Please keep your computer on."
I can't figure out what it's trying to install. This happens exactly this way, over and over, always starting at 15%, getting to 29%, then rebooting, then rolling back the changes after rebooting. I can't find any record of what it's actually trying to install. But this is getting annoying because all together it takes about 5 minutes for it to go through this process, when all I wanted to do was reboot my system quickly.
How do I determine what it's trying to install? How can I tell why it's failing? Again, when I look at Windows Update settings, it tells me there are no updates to install.
DanGoyette
2 Intern
•
28 Posts
0
August 20th, 2024 23:37
This ended up happening to me several different times after clean installs. So simply doing a clean install isn't an automatic fix for the issue.
It did, however, eventually subside. I ended up tracking the specific issue down to what I believe was an attempt by Windows Update to install language packs for various languages. I determined this by looking at C:\Windows\Logs\CBS\CBS.log, where it showed the progress I described above (starting at 15%, getting to 29 or 30%, then failing). I'm not sure if Windows Update eventually just sorted itself out, or if the fix had something to do with me manually cleaning up language packs (Disk Cleanup -> Cleanup System Files -> Language Resource Files).
In any case, this did eventually stop happening after a week. I wouldn't be surprised if this pops up again the next time I do a clean install, however. Unless this was a temporary issue that has since been corrected in Windows Update.
adcyber
1 Rookie
•
1 Message
•
2 Points
0
July 22nd, 2024 17:30
Hello
DanGoyette,
i had the same issue a few weeks ago.
It means that your windows update files are corrupted and the only fix is to do a clean windows reinstall with usb.
This is what fixed it for me and for other people.