![](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(185.6, 74%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPS%3C/text%3E%3C/svg%3E)
![](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(284.8, 27%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDG%3C/text%3E%3C/svg%3E)
Hello,
No easy answer here.
Your best bet is to use a tool like Sysinternals's Process Monitor to see what registry locations are being accessed when the error occurs and then potentially fix those keys.
Link to Process Monitor.
https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
I am not aware of an easier way to repair a corrupted registry. If it's just a single key that is unreadable, you may be able to repair it, either by editing or by exporting the key from a known good system and importing the key into this system.
Darrell