Skip to content
\n
\n \n\n \n \n \n \n\n \n \n \n \n\n \n \n \n \n\n \n \n \n \n\n \n \n \n \n\n \n \n \n \n\n \n \n \n \n\n \n \n \n \n\n \n \n \n \n
[Template_Chrome_KB5027231_fix]
Tmpl.Title=Chromium fix for Windows 11 with KB5027231
Tmpl.Class=WebBrowser
#Tmpl.Scan=u
#Tmpl.ScanUpd=KB5027231
Tmpl.ScanScript=if(system.version().major != 11) return false; return system.checkUpdates(\"KB5027231\");
ClosedKeyPath=<Template_Chromes>,HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\Shell\\Associations\\UrlAssociations\\http\\UserChoice
ClosedKeyPath=<Template_Chromes>,HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\Shell\\Associations\\UrlAssociations\\https\\UserChoice
ProcessGroup=<Template_Chromes>,chrome.exe
\n
\n
\n

\n","upvoteCount":2,"url":"https://github.com/sandboxie-plus/Sandboxie/discussions/4703#discussioncomment-12879709"}}}

Cause for concern? Messagebox: "Sandman did not finish enumerating installed windows updates last time, it probably hangs. Do you want to disable Windows Updates scanning from the software compatibility detection?" #4703

Answered by offhub
e-t-l asked this question in Q&A Feedback
Discussion options

You must be logged in to vote

Removing Windows Updates scanning from compatibility detection is not a major cause for concern for most users. This feature was primarily used in a specific compatibility template to address a Chrome-related issue caused by an outdated Windows 11 update.

Since, up-to-date systems no longer require this workaround, disabling the scan will have no noticeable effect for most users.

Template=Chrome_KB5027231_fix

[Template_Chrome_KB5027231_fix]
Tmpl.Title=Chromium fix for Windows 11 with KB5027231
Tmpl.Class=WebBrowser
#Tmpl.Scan=u
#Tmpl.ScanUpd=KB5027231
Tmpl.ScanScript=if(system.ver…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by e-t-l
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants