Share this article
Improve this guide
Failed to Read Description Error in Services.msc [Solved]
You should start by disabling fast startup, the easiest fix
4 min. read
Published onJune 18, 2024
published onJune 18, 2024
Share this article
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
In the last few days, I have come across several reports of theFailed to Read Descriptionerror in theServices.mscconsole. It’s usually followed by eitherError Code: 2orError Code: 15100, and you won’t be able to make changes to the service’s properties!
Upon closer inspection, it became evident that the problem was triggered by misconfigured boot settings, issues with the Registry, corrupt system files, or conflicting applications for native Windows services.
As for third-party services that were recently deleted, theFailed to Read DescriptionError Code: 2message is triggered after an incorrect uninstallation.
How can I fix the Failed to Read Description error in Services.msc?
1. Turn off fast startup
Many on the dedicated Malwarebytes forum confirmed thatdisabling fast startuphelped when encountering theFailed to Read Description, Error Code: 2message with the Malwarebytes service. We verified, and it works with other third-party services as well!
2. Repair the corrupt system files
If it’s thecorrupt system filesto blame for theFailed to Read Descriptionerror inServices.msc,running the DISM commandsand the SFC scan will get things up and running!
3. Uninstall any unsupported or conflicting apps
Often, third-party antiviruses and incompatible/unsupported programs trigger the Services.mscFailed to Read Descriptionerror. In one instance, it was even theAMD Driver Cleaner Tool, which has long been discontinued.
4. Modify the StringCacheGeneration DWORD in Registry
If you seeFailed to Read Descriptionfor a core Windows service, like BITS(Background Intelligent Transfer Services)or wuauserv(Windows Update Service), setting38bas the value data forStringCacheGenerationwill do the trick!
In case you don’t find theStringCacheSettingskey orStringCacheGenerationDWORD, create them.
5. Use System Restore
6. Perform an in-place upgrade
If nothing else worked, an in-place upgrade will fix the Windows serviceFailed to Read Descriptionerror. The end result is similar to reinstalling the OS, except that you won’t lose personal files and apps. Although, an in-place upgrade takes a few hours to complete!
In case this too fails, I would suggestreinstalling Windows 11. This way, all changes to the PC would be reverted to default. As for the stored files, you can move them to an external storage to avoid data loss.
Do you know any more fixes for the error? If so, share them with our readers in the comments section.
More about the topics:Services,Windows 11
Kazim Ali Alvi
Windows Hardware Expert
Kazim has always been fond of technology, be it scrolling through the settings on his iPhone, Android device, or Windows PC. He’s specialized in hardware devices, always ready to remove a screw or two to find out the real cause of a problem.
Long-time Windows user, Kazim is ready to provide a solution for your every software & hardware error on Windows 11, Windows 10 and any previous iteration. He’s also one of our experts in Networking & Security.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Kazim Ali Alvi
Windows Hardware Expert
Kazim is specialized in hardware devices, always ready to remove a screw or two to find out the real cause of a problem.
