question

BoozerBrad-5596 avatar image
0 Votes"
BoozerBrad-5596 asked AmitaMenon-3691 edited

Paging file and disk errors on Windows 10 Enterprise for Virtual Desktops

I have 2 different Azure WVD servers. Currently, every time a user logs in, they receive a warning "Windows created a temporary paging file on your computer...". I have not been able to resolve, and have let it go for a few months, until one of the disks failed and I had to restore the machine from backup. So I have declared a CC for maintenance and tried running a basic repair on the disk (Window error checking tool). It says there are error, and says it will need to reboot to resolve (of course). However, every time I run it, it come back up in about 5 minutes an still give the paging file errors. Run error checking again and it still says there are errors.

I am a little gun shy as the disk is so large it took 6+ hours to restore from backup last time.

For background, when it failed, it was unresponsive to RDP, and I couldn't access it via share or psexec. I rebooted it and it came back. I investigated and it appeared to be a driver update failure. I manually ran updates and decided to increase the paging file in an attempt to get rid of the error. After reboot, it never came back. Screenshot showed it stuck waiting for manual input for keyboard type. While I did restore it from backup, I also took a snapshot and attached it to another machine to boot it in Hyper-V. There were errors and after several hours it did repair that disk, but I did not use it as the restore came up before it was finished and production had already started for the day.

Any thoughts would be appreciated.

azure-virtual-machinesazure-virtual-desktop
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AndrewEckrich-7103 avatar image
0 Votes"
AndrewEckrich-7103 answered BoozerBrad-5596 commented

That is a easy fix,simply R.click on my computer/properties/advance/virtual memory tab/advanced/change button.With C: highlited,set to: Let system manage,click set 2X,exit,restart pc.This works for any storage drive,once enabled in: diskmgmt.msc
https://docs.microsoft.com/en-us/windows-server/administration/performance-tuning/subsystem/cache-memory-management/troubleshoot

https://docs.microsoft.com/en-us/windows-server/storage/disk-management/troubleshooting-disk-management

check out the Microsoft links above for more help...

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Sorry, but not that simple. This is an Azure virtual machine (as mentioned in first line). All VMs are created with a dual partitioned virtual HD (c: & d:) and page file is turned off on c: and set to system managed on d: (temporary space) by default. I am getting errors on the c:, not d:, and nothing resolves the issue.

0 Votes 0 ·
BoozerBrad-5596 avatar image
0 Votes"
BoozerBrad-5596 answered

OK, so thought I replied once, here I go again.

So not that easy. As I stated this is an Azure VM. The disk has 2 partitions with the secondary (d:) set as temp space. Primary (c:) has no pagefile, it is set to system managed on the secondary. This is default for all Azure VMs. My disk errors occur on the primary partition, yet never actually get resolved (according to the OS). The page file error is an annoyance and may or may not be part of the issue, but I wanted to include everything occurring with the VM.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

TravisCragg-MSFT avatar image
0 Votes"
TravisCragg-MSFT answered

Typically this error occurs when the paging file is set to a different drive than the D:/ drive (the temp drive in Azure). Make sure that your paging file is system managed, and that you are not mapping the temp drive to a different drive than the D:/ drive.

If your settings are system managed and you can see and use the temp drive without issue, your next best bet is to open a support request for someone to look further into the issue. A misconfiguration should not cause the boot failure / OS crash.

Because this was happening for both VMs, a misconfiguration is likely.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.