{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/", "slug": "dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval", "url": "https://update.dsesecurity.com/updates/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/" }, "title": "Interpret RDS User Input Delay as the slowest queued input in the interval", "summary": "What does an RDS User Input Delay counter value represent?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:14:59+00:00", "modified_at": "2026-09-08T18:23:27+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 201, "potentially_affected": "Administrators diagnosing input responsiveness on supported Windows session hosts.", "dse_recommendation": "Choose the process or session scope that matches the complaint and record its identity.", "primary_source": { "name": "Use performance counters to diagnose application responsiveness problems on Remote Desktop session hosts", "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-rdsh-performance-counters", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

The User Input Delay counter measures the time an input waits in a queue before a process handles it, and it applies to both local and remote sessions. Microsoft specifies that the reported value is the maximum delay within the configured interval, rather than the average of all inputs. The tool offers process-level and session-level counters. Microsoft documentation.

\n

Applicability

\n

Check the source’s counter-specific platform requirements and configuration notes. Identify the affected user session, application, observed time, and collection interval before comparing a reported value with a user complaint.

\n

DSE recommendation

\n

Choose the process or session scope that matches the complaint and record its identity. Ask the application owner to provide a repeatable interaction and a description of acceptable response. Retain the input-delay series alongside resource measurements from the same window.

\n

Verification

\n

Reproduce the interaction and correlate its timing with the maximum delay reported for the selected scope. Compare a normal and degraded run under known conditions. Preserve the interval and instance identifiers, and investigate the association without treating one delay spike as proof of a particular resource bottleneck.

\n

Official references

\n

Microsoft Learn: Use performance counters to diagnose application responsiveness problems on Remote Desktop session hosts. Source reviewed September 8, 2026.

", "content_text": "Source facts\nThe User Input Delay counter measures the time an input waits in a queue before a process handles it, and it applies to both local and remote sessions. Microsoft specifies that the reported value is the maximum delay within the configured interval, rather than the average of all inputs. The tool offers process-level and session-level counters. Microsoft documentation.\nApplicability\nCheck the source’s counter-specific platform requirements and configuration notes. Identify the affected user session, application, observed time, and collection interval before comparing a reported value with a user complaint.\nDSE recommendation\nChoose the process or session scope that matches the complaint and record its identity. Ask the application owner to provide a repeatable interaction and a description of acceptable response. Retain the input-delay series alongside resource measurements from the same window.\nVerification\nReproduce the interaction and correlate its timing with the maximum delay reported for the selected scope. Compare a normal and degraded run under known conditions. Preserve the interval and instance identifiers, and investigate the association without treating one delay spike as proof of a particular resource bottleneck.\nOfficial references\nMicrosoft Learn: Use performance counters to diagnose application responsiveness problems on Remote Desktop session hosts. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nThe User Input Delay counter measures the time an input waits in a queue before a process handles it, and it applies to both local and remote sessions. Microsoft specifies that the reported value is the maximum delay within the configured interval, rather than the average of all inputs. The tool offers process-level and session-level counters. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-rdsh-performance-counters).\n\n## Applicability\n\nCheck the source’s counter-specific platform requirements and configuration notes. Identify the affected user session, application, observed time, and collection interval before comparing a reported value with a user complaint.\n\n## DSE recommendation\n\nChoose the process or session scope that matches the complaint and record its identity. Ask the application owner to provide a repeatable interaction and a description of acceptable response. Retain the input-delay series alongside resource measurements from the same window.\n\n## Verification\n\nReproduce the interaction and correlate its timing with the maximum delay reported for the selected scope. Compare a normal and degraded run under known conditions. Preserve the interval and instance identifiers, and investigate the association without treating one delay spike as proof of a particular resource bottleneck.\n\n## Official references\n\n[Microsoft Learn: Use performance counters to diagnose application responsiveness problems on Remote Desktop session hosts](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-rdsh-performance-counters). Source reviewed September 8, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/", "url": "https://update.dsesecurity.com/updates/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Interpret RDS User Input Delay as the slowest queued input in the interval", "item": "https://update.dsesecurity.com/updates/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/", "url": "https://update.dsesecurity.com/updates/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/", "headline": "Interpret RDS User Input Delay as the slowest queued input in the interval", "description": "What does an RDS User Input Delay counter value represent?", "abstract": "What does an RDS User Input Delay counter value represent?", "articleBody": "Source facts\nThe User Input Delay counter measures the time an input waits in a queue before a process handles it, and it applies to both local and remote sessions. Microsoft specifies that the reported value is the maximum delay within the configured interval, rather than the average of all inputs. The tool offers process-level and session-level counters. Microsoft documentation.\nApplicability\nCheck the source’s counter-specific platform requirements and configuration notes. Identify the affected user session, application, observed time, and collection interval before comparing a reported value with a user complaint.\nDSE recommendation\nChoose the process or session scope that matches the complaint and record its identity. Ask the application owner to provide a repeatable interaction and a description of acceptable response. Retain the input-delay series alongside resource measurements from the same window.\nVerification\nReproduce the interaction and correlate its timing with the maximum delay reported for the selected scope. Compare a normal and degraded run under known conditions. Preserve the interval and instance identifiers, and investigate the association without treating one delay spike as proof of a particular resource bottleneck.\nOfficial references\nMicrosoft Learn: Use performance counters to diagnose application responsiveness problems on Remote Desktop session hosts. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:59+00:00", "dateModified": "2026-09-08T18:23:27+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-132-interpret-rds-user-input-delay-as-the-slowest-queued-input-in-the-interval/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Interpret RDS User Input Delay as the slowest queued input in the interval" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 201, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Use performance counters to diagnose application responsiveness problems on Remote Desktop session hosts", "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-rdsh-performance-counters" } } ] } }