Hi, I’m Laurel from the Digital Success team for Resolve. I’ll be sharing more updates like this focused on helping you turn new capabilities into real outcomes, and today I’m starting with a couple enhancements in Patch Management that make it easier to prioritize risk and move through remediation faster.
Before we get into it, I’d love to hear from you. What does your patching process look like today? Please share in the comments below.
We’ve made a couple of meaningful updates in Resolve across the patching workflow, focused on helping you make better decisions before deployment and move faster when issues come up. This gives you:
- Clearer prioritization, so you can quickly identify which vulnerabilities actually need attention
- Earlier visibility before rollout, so you can assess readiness and potential impact (Beta)
- Faster remediation when something fails, without digging through logs or escalating
If you’re responsible for patching, you already know the balancing act.
There’s always more updates than time, and when everything looks “important,” you’re left figuring out what actually deserves to go first. On top of that, when a patch fails, the answer usually lives somewhere inside a log file that most people don’t have time to dig through.
Let’s take a closer look at these updates.
You’ll now see CVE identifiers and CVSS severity scores directly in Patch Management, both at the device level and across your environment.
Your patch list should already feel more actionable. Patches are now prioritized by severity by default, so the highest-risk vulnerabilities surface first. Instead of jumping between tools or cross‑referencing external data, you can understand what matters and make decisions right where you’re already working.
With Pre-deployment Insights (Beta), Resolve surfaces risk, context, and readiness signals before a patch is deployed, helping you answer a question most teams are already thinking about:
Are we ready to deploy this patch?
Instead of relying on limited context or waiting to see what happens after rollout, you get early visibility into potential impact and environment readiness in one place. This doesn’t replace your process, it gives you better decision support so you can move forward with more confidence.
Pre-deployment Insights is currently in beta and will continue to evolve based on your feedback and performance. If you have feedback for us, please drop it in the comments below.
And when something doesn’t go as planned, Resolve now gives you an AI-generated summary of why a patch failed, along with guidance on what to do next.
Instead of digging through logs or escalating just to understand what happened, you get a clear explanation you can act on, so remediation doesn’t stall and you can keep things moving.
What this really changes is how you move through patching day to day, and how quickly you can go from identifying issues to resolving them.
You don’t have to cross-reference vulnerability data just to understand risk.
You don’t have to second guess which updates to prioritize.
And you don’t have to slow down your workflow just to troubleshoot failures.
Instead, you can trust your prioritization, go into deployments with better context, and take action faster when something does fail.
This is where you’ll notice the biggest difference:
- prioritize remediation based on real risk
- reduce time between detection and resolution
- assess readiness earlier before deployment
- stay aligned with security and compliance expectations
Support Articles
https://support.logmein.com/resolve/help/view-available-windows-updates-in-logmein-resolve
https://support.logmein.com/resolve/help/patch-intelligence-get-pre-deployment-insights-for-os-updates-in-logmein-resolve
https://support.logmein.com/resolve/help/view-past-windows-updates-in-logmein-resolve?highlight=AI#:~:text=Application%20and%20OS%20update%20deployments%20can%20sometimes%20fail.%20LogMeIn%20Resolve%20provides%20AI%2Dgenerated%20patch%20error%20summaries%20that%20help%20you%20quickly%20understand%20why%20an%20update%20failed%2C%20along%20with%20recommended%20mitigation%20steps.%20You%20can%20also%20download%20and%20review%20the%20log%20file%20for%20a%20more%20detailed%20investigation.
You can learn more about CVE (Common Vulnerabilities and Exposures) at https://www.cve.org/About/Overview and CVSS (Common Vulnerability Scoring System) at https://www.first.org/cvss/
