FSLogix error complains about pagefile being too small

Brass Contributor



since last week we experience an issue that on multiple session hosts FSLogix stops loading profile containers after logging the error below. The German error message reads that the page file is too small to complete the operation.


The page file is system managed with plenty of space on the disk. I was wondering if there is any guidance on this error. It started only last week and has not occurred in the last 9 months. 


Thank you.


Protokollname: FSLogix-Apps/Operational
Quelle: FSLogix-Apps
Datum: 27.04.2020 11:54:00
Ereignis-ID: 26
Ebene: Fehler
Benutzer: SYSTEM
Computer: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Failed to create driver interface worker thread (Die Auslagerungsdatei ist zu klein, um diesen Vorgang durchzuführen.)
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<Provider Name="FSLogix-Apps" Guid="{B9819571-BBB1-4F0D-965F-2BBB58B801A7}" />
<TimeCreated SystemTime="2020-04-27T09:54:00.394810300Z" />
<Correlation />
<Execution ProcessID="4668" ThreadID="5512" />
<Security UserID="S-1-5-18" />
<Data Name="Error">2147943855</Data>
<Data Name="Message">Failed to create driver interface worker thread (Die Auslagerungsdatei ist zu klein, um diesen Vorgang durchzuführen.)</Data>

4 Replies
it looks like your hosts may be running out of resources. Are there any other event logs errors from other components that indicate your hosts are low in resources?

@Soo Kuan Teo Hi, no. At the time the memory usage was around 40% on a 64GB machine. Four users where logged in. There might be high utilization from WIndows Search because the four users logged in in short intervals.


It happened on two different hosts within three days and in both instances after the April Windows Updates. Two other hosts are running fine and not have shown this problem (yet). 


All other logs are fine. This is the only error at this time. Users were able to log in with temporary profile. We had the users log off, remove the temp profiles, rebooted the server and had no other problems since (or so far).


I was just surprised by the same error on two machines within a matter of days even with less load than usual.  



Can you please share the tenant name and your sessionhosts name? I would like to take a look at your FSLogix logs. You can replace some characters with * so your info are not fully disclosed.

@Sascha Stops Hello. We've started to randomly experience the same issue. Did you ever find a cause or resolution?