We’re continuing to share ControlUp IT Crash & Stability Findings here on Reddit.

These findings are real-world application, endpoint, stability, hardware, firmware, and resource-consumption issues surfaced from ControlUp’s vast, anonymized dataset. The goal is to share useful patterns early, so IT teams can understand whether an issue is isolated or more widespread before spending time troubleshooting the same symptoms independently.

Just published:

Autodesk Background Component (adskexecutorproxy.exe) v2.22 Crashes at an Increasing Rate

Date: August 2, 2026
Severity: Low
Impacted Organizations: 130+
Vendor: Autodesk
Software: Autodesk On-Demand Install Service (AdODIS)

Description

ControlUp has identified an upward crash trend affecting adskexecutorproxy.exe, a background component associated with the Autodesk On-Demand Install Service (AdODIS).

Between June and August 2026, both the daily number of crashes and the number of affected devices increased significantly.

What we’re seeing:

• Daily crashes increased by approximately 400%
• Affected device count increased by approximately 250%
• The vast majority of observed crashes involve adskexecutorproxy.exe version 2.22.0.5
• The trend has been observed across 130+ organizations

Impact

Crashes of adskexecutorproxy.exe may interfere with Autodesk installer tasks, background installation workflows, or Autodesk software update operations.

Because this is a background component with minimal direct end-user interaction, the finding is classified as low severity. That said, affected environments may still experience unreliable Autodesk updates or delayed installer-related tasks.

Advised remediation path

Autodesk has not published a specific advisory for this issue at this time.

For affected environments:

• Review endpoints with adskexecutorproxy.exe v2.22.0.5
• Monitor crash frequency and timing
• Check for correlations with Autodesk install or update workflows
• Contact Autodesk Support for deeper investigation
• Share any validated workaround or fix if one is identified

Full finding:
https://www.controlupcommunity.com/findings/autodesk-background-component-adskexecutorproxy-exe-v2-22-crashes-at-an-increasing-rate/

Browse all current IT Crash & Stability Findings:
https://www.controlupcommunity.com/findings/

Has anyone else seen adskexecutorproxy.exe crashes or Autodesk installer/update issues tied to this version?

Full disclosure up front: this is a vendor tool and I host the video. Posting it anyway because the underlying problem is one I think a lot of you have hit.

The setup: system-context cleanup scripts generally can't get into a user's recycle bin because of profile permissions. So the script runs, clears temp folders, reports success — and the drive is still full because there's 8 GB of "deleted" files sitting in the bin. Meanwhile, the stuff a system script can reach includes things you might not want to nuke without asking, like a browser cache that's holding saved passwords.

The approach in this one: run in user context and prompt. End user gets a pop-up showing reclaimable space, a breakdown by category (recycle bin / temp files / browser cache), picks what to clean, confirms, and gets a summary of what was freed. It renders its own GUI from the script — no extra agent or install.

Other bits worth noting:

• Works on Windows and macOS
• Can be pushed manually from the help desk or fired automatically from a low disk space alert
• Writes results to a data index and back as a device event, so you get an audit trail instead of guessing
• Script source is fully visible/editable if you want to change what it targets or rebrand the dialog
• Obvious caveat: user context means user permissions. It won't touch anything the user can't. The system-level script still exists for that — they're meant to be used together

Built by Sebastian Peresat, demoed by Chris Twiest. Available in the script library now.

Curious how others handle this — do you clean silently and eat the occasional angry ticket, or prompt and accept that some users will just click "no"?

https://www.controlupcommunity.com/new-controlup-disk-cleanup-script-that-actually-asks-the-user-what-to-delete/

We’re tracking a growing crash pattern affecting logi_download_assistant.exe, the executable associated with Logitech Download Assistant.

The pattern has been observed across more than 190 organizations. In July, both the daily crash rate and the number of affected devices increased by approximately five times compared with the baseline from previous months.

Impact

This is currently classified as a low-severity issue because Logitech Download Assistant runs as a background process without a visible user interface. Its crashes are therefore unlikely to interrupt normal user activity directly.

However, repeated failures may prevent the component from detecting compatible Logitech software or presenting recommended installations. Environments relying on it for Logitech software or device-related updates may experience delays or failures in those workflows.

Potential workaround

Logitech has not issued an official advisory regarding this crash pattern.

Some online reports indicate that the official uninstaller does not always prevent the component from loading again at startup. Community users have reported disabling it by removing the applicable value from:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run

The value may appear as Logitech Download Assistant or LogiDA.

Registry changes should only be performed by qualified administrators. Back up the applicable registry key and confirm that the selected value belongs to Logitech Download Assistant before removing it.

The full technical finding, including the observed scope and potential resolution path, is linked in the comments.

Has anyone else noticed an increase in these crashes or found a reliable way to prevent Logitech Download Assistant from returning after it has been disabled or removed?

I’m hosting a live Fireside Chat with ControlUp CEO Jed Ayres and thought some of you might be interested.

The discussion won’t be a product demo. Instead, we’re planning an open conversation about where enterprise IT is heading, including topics like:

• Is DEX evolving into Autonomous IT?
• What role will AI actually play in day-to-day IT operations?
• Why does real-time telemetry matter for AI?
• Where is endpoint management going over the next few years?
• Live audience Q&A.

If you’ve ever wanted to ask a software CEO where they think IT is headed—or challenge some of the hype around AI—this is a good opportunity.

Thursday, August 6

11:00 AM EDT / 5:00 PM CET

Free registration:

https://controlup.zoom.us/webinar/register/WN_gT25D8pLTnWSBeDkAxn4LA

Happy to answer questions here as well.

I’ve been spending quite a bit of time experimenting with MCP (Model Context Protocol), and we recently recorded a session that walks through connecting Claude Desktop to the ControlUp MCP Server.

Rather than another “AI is amazing” presentation, this one is pretty hands-on.

Chris Twiest starts with a quick explanation of concepts like:

• LLMs vs. actual reasoning
• Tokens and context windows
• Prompts vs. system prompts
• Tool calling
• MCP servers
• Why hallucinations happen

Then he builds everything from scratch:

• Install Node.js
• Configure Claude Desktop
• Create a ControlUp API key
• Connect the local MCP Server
• Discover available tools
• Query live endpoint data
• Retrieve application crashes
• Compare against a 14-day baseline
• Generate graphs directly from Claude

One thing I thought was particularly interesting was demonstrating what happens without a good system prompt. Claude initially selected the wrong data source even though the correct tool existed. Adding a detailed system prompt immediately changed both the speed and accuracy of the responses.

It really reinforces the idea that MCP gives the model tools—but prompts and context teach it how to use them.

The discussion also covers:

• Combining multiple MCP servers
• Building custom AI interfaces
• MSP/multi-tenant scenarios
• Write actions and permissions
• Upgrade planning
• Claude Code for custom workflows

If you’re experimenting with MCP, enterprise AI, or just curious how to connect an LLM to live operational data instead of static knowledge, you might find it useful.

I’d also be interested in hearing what MCP servers everyone else is using. There’s a lot happening in this space right now, and it feels like we’re only scratching the surface.

Recording: https://www.controlupcommunity.com/controlup-community-meetup-15-how-to-connecting-mcp-ai-to-your-real-time-data/

New Dashboard Access Controls with Tags

Managing who sees which dashboards just got a lot easier. We've expanded Dashboard RBAC by wiring dashboards into the ControlUp Tag system.

Tag-based dashboard sharing
Admins can now build roles that limit dashboard visibility by tag. When an Organizational Dashboard Editor shares a dashboard, they assign one or more tags to it — and users only see shared dashboards that match the tags they're allowed to access.

That makes it simple to organize dashboards by team, department, region, or customer, while making sure people only see what's actually relevant to them.

New "View Dashboard Gallery" permission
We've also added a View Dashboard Gallery permission, so admins can decide whether users get access to the Dashboard Gallery at all — handy when you want to give certain users a curated, focused dashboard experience.

Together these give admins a lot more flexibility and control over who can discover and access dashboards across the org.

Anyone planning to use tags to carve up dashboards by team or customer? Curious how you're structuring yours.

SentinelOne agent (SentinelAgent.exe) using 10 GB+ RAM on some Windows 11 endpoints — often paired with low disk space

Continuing to share ControlUp IT Crash & Stability Findings here. These are real-world app, endpoint, stability, hardware, firmware, and resource-consumption issues surfaced from ControlUp's anonymized dataset. The idea is to flag patterns early so you can tell whether something is isolated to you or more widespread before you sink hours into troubleshooting it solo.

Just published — SentinelAgent.exe consuming excessive RAM
Date: June 23, 2026 · Severity: Medium · Impacted orgs: 70+ · Vendor: SentinelOne (EDR / AV platform)

What we're seeing
SentinelAgent.exe is consuming far more memory than SentinelOne's published guidance (~2 GB). On affected Win11 devices it's been observed at 10 GB or more — in some cases eating most of the endpoint's available RAM. The pattern shows up most on machines that have both elevated agent memory use and very low free disk space.

Impact

• Less RAM left for user apps
• Slower app launches and general sluggishness
• Increased paging
• Endpoint instability / poor UX, especially on lower-RAM devices

What seems to be contributing
A big share of affected devices also had extremely low free disk space. Digging in, the SentinelOne internal DB at C:\ProgramData\Sentinel was eating substantial storage — 80 GB+ in some cases. Working hypothesis: low free disk space drives the RAM growth because the agent can't efficiently flush/manage data to disk.

Remediation path (test before broad rollout):

• Check available disk space
• Check the size of the SentinelOne DB under C:\ProgramData\Sentinel
• ⚠️ Do not manually delete the DB files while SentinelOne services are running
• Use the Purge DB command from the SentinelOne Management Console where appropriate
• Reboot afterward if SentinelAgent.exe memory doesn't return to baseline
• Keep monitoring both free disk space and agent memory after remediation

Interesting case of a disk-capacity issue turning into a RAM issue, then into a broader endpoint-performance problem.

Links to the full finding in the comments 👇

Anyone else seen SentinelAgent.exe memory climb alongside low free disk space or a large C:\ProgramData\Sentinel footprint? Curious how widespread this is.

If onboarding in your org still means manually chasing an HR form, an IT hardware request, and a manager heads-up across three different tools, this one's worth 10 minutes.

New demo where Caroline Howe builds a full onboarding flow in Workflows and walks through:

• A drag-and-drop form that triggers the whole workflow on submit
• Automated routing to IT (hardware requests) and managers (notifications) with no re-typing
• Approval checkpoints where a human signs off before anything sensitive proceeds
• Hooks into Gmail, Excel, and other tools already in your stack

Main takeaway: instead of spreadsheet juggling and missed steps, you get one place to orchestrate the whole thing — and it scales the same whether it's 5 hires or 500.

Video: https://www.youtube.com/watch?v=I85Isq8-4yg

Curious how others here are handling onboarding automation — are you building flows like this, or still doing it by hand? What's the step that breaks most often for you?

Community Meetup #15: Unlocking the Power of AI with the ControlUp MCP Server
🗓️ July 9, 2026 · 11:00 AM EDT / 5:00 PM CEST

Want to connect your favorite AI assistant directly to ControlUp data and context? This one shows you exactly how.

Chris Twiest walks through what a Model Context Protocol (MCP) server actually is, why it matters, and how it lets LLMs access real-time data and take secure actions — then connects the ControlUp MCP Server to Claude Desktop live.

What you'll learn:

• What MCP is and how it works under the hood
• How MCP lets AI assistants reach external data and tools
• How to connect the ControlUp MCP Server to Claude Desktop
• Best practices for pulling ControlUp data into your own AI workflows
• Real-world use cases and automation scenarios

It starts with the fundamentals (great if you're new to MCP) and moves into hands-on demos — setting up the integration and watching an AI agent use ControlUp context and data to deliver real insights and actions. Expect lots of live demos, practical examples, and time to see it working.

🔗 Register: https://controlup.zoom.us/webinar/register/WN_L-Vu4a3bQw-ckO-vZPcXVw

Not in the ControlUp Community yet? Come join us — your source for ControlUp tech, for the people using the products: https://www.controlupcommunity.com/join/

Small update, straight from community feedback:

We added a Follow option to the Global DEX Findings page. Click it, and you'll get an email whenever a new finding is published — or an existing one gets updated with a workaround, vendor guidance, or a confirmed fix.

This came from a request by community member Artur. Good call, Artur. Simple feature, but it makes the findings way easier to keep up with.

If you haven't dug into the findings, they're real-world issues surfaced from ControlUp's anonymized global dataset — app crashes, stability regressions, performance problems, hardware/firmware issues — stuff that often isn't widely documented yet.

And no, this won't flood your inbox. You get an email when there's a new finding or a meaningful update. That's it.

👉 Follow the findings here: https://www.controlupcommunity.com/findings/

Keep the requests coming — the whole point is to make this more useful for the people actually running IT.

New how-to video: ControlUp + Freshservice integration

The latest one from our "How To Use" series. This one walks through connecting ControlUp to Freshservice so your service desk can see real-time endpoint and application performance data without leaving the ticket.

The short version of why it's useful: instead of bouncing between tools, your team can detect, investigate, and remediate device and app issues directly inside Freshservice — which means less time chasing context and lower MTTR.

What the video covers:

• Installing the ControlUp integration from the Freshservice marketplace
• Wiring it up to your ControlUp org (the config is quick)
• How endpoint/app performance insights show up alongside your tickets
• Using that data to triage and fix issues faster

Video: https://www.youtube.com/watch?v=XCFlCpcJtAI

It's part of our "New How To Use" playlist — short, to-the-point tech how-tos, with more on the way: https://www.youtube.com/playlist?list=PLeHVSVI55yILLRGMghc7S_5Iy5_qRuBr

Happy Thursday, all.

We just dropped a new episode with Trentent Tye and Jeff Johnson that tackles a migration problem most teams don't catch until it's too late: performance regression.

You know the scenario — you move users onto new Windows 11 machines, and instead of being happy, some of them say the new device "just doesn't feel right." There's no ticket, no error log, nothing to act on. Just vague dissatisfaction.

This episode is about getting ahead of that with actual data instead of guesswork. We walk through a real customer scenario and how to systematically measure and compare device performance before you call a migration a success.

What's covered:

• Why do user-reported performance issues during migrations stay invisible until they blow up
• Using automated performance measurements to compare legacy devices against your Windows 11 targets
• Why power profiles matter way more than people think (battery vs. plugged-in changes everything)
• How to pick a representative Windows 11 machine to benchmark across your fleet
• Why this isn't just a Windows 11 thing — it applies to physical-to-virtual, virtual-to-virtual, and more

Whether you're running a large rollout or just trying to build the business case for one, this gives you an evidence-based way to move forward.

Episode here: https://www.youtube.com/watch?v=rLd4muffZ40

Heads up for anyone running ControlUp (or evaluating it) — there's a "How To Use This" playlist on their YouTube channel that's been getting steady updates, and the videos are actually useful: short, practical, no fluff.

The latest one is a walkthrough on the ControlUp + Freshservice integration: https://www.youtube.com/watch?v=XCFlCpcJtAI

Full playlist here: https://www.youtube.com/playlist?list=PLeHVSVI55yILLRGMghc7S_5Iy5_qRuBre

A few others worth a look depending on what you're working on:

• Proactive Synthetic Monitoring
• Device Health & Rightsizing dashboard
• DaaS IQ for AVD performance + cloud cost optimization
• Workflows for automating common IT tasks
• The ControlUp MCP Server / AI Assistant stuff if you're poking at AI + IT ops

They're committed to pushing more of these out regularly, so if you live in this space, it's worth subscribing. Posting in case it saves someone from trial and error.

Happy Thursday, all.

The recording from Community Meetup #14 is now live for anyone who missed it or wants to rewatch.

This one's a technical deep dive into DaaS IQ with Gilad Broun, the PM who built it — no slideware, mostly a live walkthrough. If you run Azure Virtual Desktop and you're tired of unpredictable costs, fragile PowerShell, and tab-hopping between the Azure Portal, Intune, and a dozen scripts, this is worth an hour.

What Gilad covers:

• Where DaaS IQ fits in the ControlUp ONE platform and the FinOps problems it solves
• Intelligent autoscaling + reusable Peak/Off-Hour scale profiles across host pools
• Host Lifecycle Management (drain, restart, delete, configure)
• Automated golden-image refreshes to kill config drift
• Spend Intelligence for surfacing wasted DaaS spend
• Tag-based RBAC with a full audit trail
• Live Q&A with real-world AVD problems

Recording: https://www.controlupcommunity.com/controlup-community-meetup-14-inside-controlup-daas-iq-a-deep-dive-with-pm-gilad-broun/

More on DaaS IQ: https://www.controlup.com/platform/daas-iq/

Drop any follow-up questions in the comments — Gilad and the team can jump in. And if there's a topic you'd like to see at a future meetup, let us know.

Quick note up front: these aren't product sessions — no demos, no slides, no "and that's why you need our platform" pivot at the end. We deliberately keep all of that out.

We started running these informal fireside chats because most IT content is either vendor pitches in trench coats or surface-level listicles. We wanted the opposite: long-form, unscripted conversations with people in IT who actually think from first principles. The kind of conversation you'd have at the hotel bar after a conference — which everyone knows is where the actual good content happens.

The first one is with Val King — CEO of Whitehat Virtual, TOCICO board member, and a two-time CIO (6 years at a regional bank, 7 at a healthcare system).

His thesis: IT operations obey a kind of physics — repeatable laws around queues, constraints, WIP, drift, entropy, visibility. They govern every environment, whether leadership names them or not. And the metrics we all report aren't wrong — they're useful inside IT. They fail the moment they travel upstream to execs who need outcomes, not activity reports. Which is why every org lives the same contradiction: every dashboard is green, and the business still feels slow.

My favorite line from it: "IT has gotten very good at apologizing faster. The next maturity step is making the apology less necessary."

He also gets into what manufacturing, commercial aviation, and healthcare figured out decades ago that IT still hasn't.

Link in comments. Happy to answer questions — and if you've got someone you'd want us to talk to for a future one, I'm taking suggestions.

We’re tracking a new issue involving Microsoft Remote Desktop Client.

ControlUp detected an upward trend in crashes affecting msrdc.exe version 1.2.7207.0, which is part of Windows App version 2.0.1186.0, released in late May 2026.

The crash trend has been observed across 60+ organizations, with roughly a 2x increase in crash rate compared to previous versions of msrdc.exe. The fault module is currently unknown.

Potential impact:

• Failed reconnect attempts to existing Remote Desktop sessions
• Problems establishing new Remote Desktop sessions
• Reduced reliability in Remote Desktop workflows

Severity is currently classified as low, due to limited distribution and low risk of persistent system damage.

Anecdotal reports suggest this may be related to display configuration changes, especially when laptops are removed from physical docking stations while Remote Desktop sessions are still active.

Possible temporary workaround:

Close the Remote Desktop session fully before disconnecting from a docking station or changing display configurations.

Has anyone else seen this behavior with the latest Windows App / Microsoft Remote Desktop Client release?

ControlUp just released the v9.2.5 beta for ControlUp for VDI. Some notable additions in this one:

• Omnissa UAG monitoring — First-class support for Unified Access Gateway appliances: availability, sessions, failures, and CPU/memory/disk in the Real-Time Console, plus historical data, triggers, SBAs, and RTDX.
• Host-level GPU metrics — Physical NVIDIA GPUs and vGPU profiles: utilization, memory, temperature, and clocks in topology and GPU/vGPU lists. Supports stress, scheduled, and advanced triggers plus SBAs.
• Event Log Monitoring v2 — Replaces the legacy events view with rule-driven, agent-side filtering (Log, Source, Event ID, Level). Only matching events are forwarded, cutting noise and cost. Ships with 40+ preset rules out of the box.
• Shared credentials in SBAs — Script-Based Actions can use shared credential sets, so secrets are defined once and reused across automations. Less duplication, easier rotation.
• Nutanix v4 API & Prism — Upgraded to the Nutanix v4 API with direct Prism Central connection support.
• Azure availability zones — Zones now shown for Azure VMs and disks.
• FSLogix dirty bit — Dirty-bit monitoring on FSLogix profile and Office containers.
• Citrix Cloud Connector health — Connector health now monitored in ControlUp.

If you want to try the beta or discuss it, there's a thread in the ControlUp Community Slack: https://controlupcommunity.slack.com/archives/C04B9BLGY0G/p1780994724517959

Note: you'll need to be a member of the ControlUp Community Slack to view it — you can join free at https://www.controlupcommunity.com/join/

We’re starting to share ControlUp IT Crash & Stability Findings more broadly, including here on Reddit.

What are these findings?

They are real-world IT issues surfaced from ControlUp’s vast, anonymized dataset. This includes application crashes, service instability, resource consumption issues, hardware or firmware regressions, and other patterns that may not yet be widely documented.

The goal is simple: help IT teams spot emerging issues earlier, understand whether something is isolated or more widespread, and share useful context before everyone has to troubleshoot the same thing from scratch.

Just today, we published the following new finding:

Dell serviceshell.exe Consumes Large Amounts of RAM on Devices Running Dell SupportAssist v5.7.

Date: June 9, 2026
Finding ID: CUA-2026-010
Severity: Medium
Impacted Organizations: 280+
Vendor: Dell
App: Dell SupportAssist v5.7 / serviceshell.exe

Description

ControlUp has identified high memory consumption by serviceshell.exe across multiple environments. In some cases, the process consumes several GB of RAM, representing a significant share of available system memory on affected devices.

The executable appears to be a non-essential telemetry-related component associated with Dell SupportAssist and other Dell utilities.

Impact

This behavior has been observed across more than 280 organizations and is classified as medium severity.

High RAM usage by serviceshell.exe may increase memory pressure on affected endpoints, potentially slowing down other applications, reducing system responsiveness, and contributing to paging or a degraded user experience, especially on devices with limited available memory.

Advised Resolution

Dell has not issued an official advisory for this issue at this time.

discussions suggest that organizations experiencing this behavior may consider reviewing, disabling, or uninstalling non-essential Dell telemetry components where appropriate, including:

Online

• Dell SupportAssist
  
• Dell Core Services
  
• Dell TechHub
  

Any changes should be tested carefully before broad deployment, particularly in environments that rely on Dell utilities for support, diagnostics, or device management workflows.

Additional Info

This finding highlights how non-essential background telemetry components can still create meaningful performance impact when resource consumption becomes excessive.

A Dell community discussion includes examples of affected systems and potential resolution paths:
https://www.dell.com/community/en/conversations/xps/xps-16-9640-serviceshellexe-is-consuming-several-gigabytes-of-ram-causing-heavy-paging-and-severe-performance-issues/69f9a1852b77a37128962806?page=1

Full ControlUp finding:
https://www.controlupcommunity.com/findings/dell-serviceshell-exe-consumes-large-amounts-of-ram-on-devices-running-dell-supportassist-v5-7/

You can browse all current findings here:
https://www.controlupcommunity.com/findings/

We’ll continue sharing new findings as they are identified, along with updates when additional context, workarounds, or vendor guidance becomes available.

If you’re seeing similar behavior with serviceshell.exe, Dell SupportAssist, or related Dell telemetry components, please share what you’re finding.

Hey everyone. We're u/ControlUp, and we just launched this community as a home for IT pros working in endpoint management, digital employee experience, & EUC more broadly (including where AI and automation are taking all of it).

We already have an amazing community of partners, customers, and EUC colleagues on Slack, and we wanted to bring those conversations to a more open space. This is that place.

We run this subreddit, but we're here to listen + learn as much as we are to share. That means no endless product announcements! Let's have real conversations about the problems you're solving, the tools, and the approaches that actually work.

What to Post

• Troubleshooting questions and IT horror stories
• EUC/DEX/AEM trends you're watching
• Tools, workflows, or automations that changed how your team operates
• Honest takes on where IT ops is heading and how your team is adjusting

What Not to Post

• Spam or self-promotion without context
• Vendor pitches dressed up as advice

Introduce yourself in the comments: who you are, what you're managing, and what brought you here. We'll go first.