12/28/2022 0 Comments Foricbly enable readyboostI mean, it literally says the Registry was corrupted □ Going through it was pretty obvious that it was registry corruption:įiltering for EventID 5 shows all the attempts of booting to BSOD: I then deleted this version, and booted into the system and looked at Event Viewer for hints of what could be at fault. So I tried it a few more times, because, why not? Since this was a PVS target device, the easy method was deleting the version and trying to upgrade PowerShell to 5.1, which resulted in the same BSOD. I have encountered this issue before, but I haven’t recorded my troubleshooting steps until now. Upon reboot I encountered a bluescreen with code 0xF4: The issue seemed innocuously enough, we upgraded PowerShell to 5.1. I encountered an interesting issue and worked through a solution with a corrupt registry. Sc.exe sdset streamservice $sd.GetSddlForm(3) $sd.DiscretionaryAcl.InsertAce($serviceCount, $systemCommonAce) $serviceCount = $sd.DiscretionaryAcl.Count $Sddl = sc.exe sdshow StreamService | where Write-Host "Listing permissions for StreamService: `r`n" -ForegroundColor Yellow GenericRead = ACL of the streaming service and present it
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |