<![CDATA[[Solved] Windows 20H2 20H2 Build 19042.746 not tagged Insecure]]>Hi,

Latest "secure" W10 20H2 is 20H2 Build 19042.804.

20H2 Build 19042.746 is still flagged "OK".

Hope this helps.

]]>https://vulndetect.org/topic/1033/solved-windows-20h2-20h2-build-19042-746-not-tagged-insecureRSS for NodeThu, 16 Jul 2026 02:23:55 GMTWed, 10 Feb 2021 14:06:21 GMT60<![CDATA[Reply to [Solved] Windows 20H2 20H2 Build 19042.746 not tagged Insecure on Sun, 14 Feb 2021 17:50:06 GMT]]>OK, then I mark this issue as solved.

]]>https://vulndetect.org/post/4128https://vulndetect.org/post/4128Sun, 14 Feb 2021 17:50:06 GMT<![CDATA[Reply to [Solved] Windows 20H2 20H2 Build 19042.746 not tagged Insecure on Thu, 11 Feb 2021 17:08:59 GMT]]>@tom : You are right!
@OLLI_S So can be moved to fixed issues.

]]>https://vulndetect.org/post/4125https://vulndetect.org/post/4125Thu, 11 Feb 2021 17:08:59 GMT<![CDATA[Reply to [Solved] Windows 20H2 20H2 Build 19042.746 not tagged Insecure on Wed, 10 Feb 2021 21:08:48 GMT]]>@gregalexandre We base the security state of Windows on what the Windows Update API reports.

We have found that it sometimes reports all to be OK, even if you haven't rebooted your machine to fully apply the latest updates.

I suppose this is the case here.

]]>https://vulndetect.org/post/4120https://vulndetect.org/post/4120Wed, 10 Feb 2021 21:08:48 GMT