Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Error Job <JobName> cannot be started. SessionId: <UUID>, Timeout: [361 sec]
Managed session <UUID> has failed
Error Job <JobName> cannot be started. SessionId: <UUID>, Timeout: [361 sec]
Error Job [Infrastructure update] has failed to start. Timeout expired (6 minutes). SessionId: <UUID>
Log Name: System
Source: Win32k
Event ID: 243
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer:
Description:
A desktop heap allocation failed.
NT AUTHORITY\SYSTEM
context. If the Windows OS is running out of Desktop Heap memory, new processes can't be started.
This article is relevant to a specific scenario where the Windows OS suffers from a 'heap allocation' failure.
The solution provided in this article should only be performed if Event ID# 243 is found in the Windows System Event Logs (eventvwr.msc).
The Desktop Heap size must be increased via a registry modification.
Because this change will affect the desktop heap of all services (also known as non-interactive window stations), do not make the new value larger than necessary.
Your feedback has been received and will be reviewed.
Please try again later.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.