Windows Update is rarely just a technical job on vessels.
It affects bandwidth, timing, crew systems, operational PCs, and support planning.
That is why we added a fleet KB approval workflow to Cyber Detective Portal 2.
What changed
Admins can now add a Windows Update KB once and manage its release state from the portal.
The approval list keeps the useful parts visible:
- Windows version
- KB number
- release date
- size
- fixes
- known issues
- publication state
Once a KB is approved for a fleet, the other update system can read that decision and act on it.
The portal stays as the control point.
The update delivery system still does the delivery work.
Why it matters
This gives teams a clearer handover between review and rollout.
A KB can be tested, sandboxed, approved, and then exposed as an approved fleet update without needing people to pass decisions around manually.
That reduces ambiguity.
For vessel patching, that is a very good thing.
Bottom line
Cyber Detective Portal 2 now provides a simple approval layer for fleet Windows Update decisions.
It is deliberately lightweight: approve the KB, keep the flag clear, and let the rollout system do the heavy lifting.