Share this article
Improve this guide
What is Event ID 158 & How to Fix it Quickly
Learn how you can resolve the Event ID 158
5 min. read
Updated onOctober 4, 2023
updated onOctober 4, 2023
Share this article
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Key notes
Multiple users have reported coming across an Event ID 158 error event in the Windows event logs. This event message pops up every 5-10 seconds on joined computers.
In this guide, we will share with you the details that will help you understand what this Event ID 158 means and how you can quickly resolve it. Let us get right into it.
What is event ID 158?
According toMicrosoft, the Event ID 158 that pops up in theWindows event logsindicates that two or more physical disk devices in Windows 11 or 10 are assigned identical disk GUIDs. Event ID 158 is also known as Disk Signature Collision.
GUID stands for Globally Unique Identifier and is a 128-bit integer number to identify resources. It is a common term that is used by developers working with Microsoft technologies. Others use UUID which stands for Universally Unique Identifier.
Notably, Event ID 158 does not have any functionality or performance impact on Windows PCs. It just warns you that two or more disk devices are sharing identical disk GUIDs.
What are the possible causes of Event ID 158?
This problem can be caused by any of the below-mentioned reasons:
Let us now take a look at the most effective solutions that will help you resolve the Event ID 158 issues on your Windows PC.
How to Fix Event ID 158?
1. Enable MPIO
In order to fix the Event ID 158 Windows event log, you need to have the Server Manager installed on your computer.
Many users weren’t able to find the Server Manager inside the Administrative Tools section because it wasn’t installed in the first place.
Follow the above steps to install the Windows Server Manager on your PC. We have a guide that explains some other methods via which you caninstall the server managerand cross-check if all components of the Server Manager were installed on your PC or not.
Following the above steps you make sure that the MPIO or the Multipath I/O is enabled on your PC, which is the main reason why you were getting the Event ID 158 issue.
2. Run the ResetDiskIdentifier parameter
3. Update the chipset driver
Multiple users have reported that after updating their chipset drivers, they were able to resolve the Event ID 158 issue on their PCs.
That is it from us in this guide. We have a guide that explains how you can easilyresolve Event ID 4103and what causes the problem.
You can also check out our dedicated guides that will help youfix Event ID 16andEvent ID 10010along with their root causes.
Feel free to drop a comment below and let us know which one of the above solutions resolved Event ID 158 on your client systems.
More about the topics:event log viewers
Sagar Naresh
Sagar is a web developer and technology journalist. Currently associated with WindowsReport and SamMobile. When not writing, he is either at the gym sweating it out or playing country music on his guitar.
He is an avid traveler and has been to 15 countries, going to more places soon. TRAVEL and WORK is his mantra for a peaceful life.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Sagar Naresh