Important Notice: Windows Updates on Toolbase Systems - please wait 2-4

Please apply newly released Windows patches on the Windows PCs inside our Toolbase vending systems no earlier than 2-4 weeks after release. Before rollout, check for known issues and validate in a safe test environment.

Background


Our Toolbase dispensing systems ship with a Windows PC. Customer IT teams manage patching. We have repeatedly seen that installing updates immediately at release can cause operational issues - up to service disruption of our software and machines.


Recommendations (Best Practices)
1. 2-4 week deferral: Deploy monthly quality updates and out of band fixes only after 2-4 weeks. 
       Many early issues surface and are addressed during this window.
2. Pre rollout information check: Review reports of known problems, e.g.:
       Born's IT & Windows Blog (German): www.borncity.com/blog/
       BleepingComputer - Windows Update: www.bleepingcomputer.com/tag/windows-update/
       TechSpot - Windows Update: www.techspot.com/tag/windows+update/
3. Controlled rollout:
       Test on a non production system first (same build, drivers, and software).
       Schedule a maintenance window.
       Take full backups/system images and prepare a rollback plan.
4. Coordination & communication:
       Notify production stakeholders in advance.
       For major updates or driver rollouts, please inform our support ahead of time (see contacts below).
5. Conservative update settings (suggested):
       Defer quality updates by 2-4 weeks (WUfB/MDM/GPO).
       Disable Preview/C/D releases in production.
       Do not auto deploy driver updates; install only after verification.


Why 2-4 weeks?
Most incompatibilities (e.g., printing subsystems, networking stacks, .NET runtimes, drivers) tend to appear within the first days. A short, planned delay significantly reduces risk without sacrificing security.


Exceptions (critical security fixes)
For critical vulnerabilities, a faster response may be justified. In that case:
 - Test in staging first.
 - Verify backup/restore.
 - Prepare rollback and comms.
 - Contact support if unsure about impact on our software/machines.


Minimum process
1. Patch released ? start a 2-4 week timer.
2. Monitor the sources above for known issues.
3. Staging test: our software, peripherals (scanners, scales, RFID, network shares), printing/labels, services, scheduled tasks.
4. Approval by IT/production ? rollout in maintenance window.
5. Post checks (smoke test) and documentation.