SMART 2.0.0.10October 2025

📋 What’s New

🐛 Fixed Bugs

🛠 Notes & Recommendations


SMART 2.0.0.9 August 2025

Highlights:

🚀 Introducing SMART 2.0.0.9: Driver Boost, Better Logs & Autopilot Warnings that Actually Matter

The latest SMART update is here, and it’s a big one.

SMART 2.0.0.9 introduces Driver Boost, our powerful new multi-threaded driver installation engine, Friendlier Error Logging that tells you exactly what went wrong and why, and a critical new Autopilot Local Profile Detection system that helps you catch hidden profile locks before they become a GDPR disaster.

🔧 DRIVER BOOST Technology

Multi-threaded driver installation

Gone are the days of downloading and installing drivers one-by-one. SMART 2.0.0.9 introduces Driver Boost, our new multi-threaded engine that downloads and installs multiple drivers simultaneously.

What this means for your team:

Behind the scenes, we’ve rebuilt the driver engine to utilise parallel downloads and installations, so your techs aren’t waiting on slow, serial installs. The result? Faster refurb. Faster sales.

🧩 Friendlier Error Logging

Know what went wrong. Fix it faster.

When something fails during deployment, SMART now makes it crystal clear:

We’ve made SMART more transparent, so your team can fix problems in seconds, not hours. No more vague errors or mystery failures.

⚠️ Autopilot Local Profile Detection

Catch hidden Autopilot profiles before they cause data breaches

This is a huge one. SMART 2.0.0.9 now checks the local registry for existing Autopilot profiles and warns you immediately at the top of the app if one is detected, before and after key injection.

Why this matters:

Devices that were previously Autopilot-enrolled (e.g., ex-corporate or EDU stock) often retain local profile data such as:

If these are not removed, your customer may boot up and see someone else’s personal information, which is a serious GDPR risk and a quick way to lose trust.

SMART gives you a clear opportunity to spot and remove this before resale.

🔍 Important Note: Cloud vs Local Lock

This feature only checks for Autopilot profiles stored locally in the registry, it does not confirm cloud enrolment status.

That’s important because:

If you inject a key and sysprep a device while a local profile is present, and the buyer powers it on without internet access, the device can’t “call home” to confirm the lock is cleared. It may still show the lock screen, even though the cloud lock is gone.

SMART now warns you in advance, so you can:

This gives your team a crucial second chance to avoid compliance issues and frustrating returns.

🧠 Ready to Try It?

Update to SMART 2.0.0.9 and see the difference — or if you’re not yet using SMART to streamline licensing, driver installs, and lock detection, book a demo and see what you’re missing.