Hi
Really weird problem.
When changing location of the windows page file and rebooting, windows will give the error: "windows created a temporary paging file on your computer because of a problem that occurred".
I have tried pretty much every combination of disk controller/MBR/GPT/Allocation unit Size/Page file size there is.
Anyone tried or able to reproduce the issue?
/Kristian
I have the same issue on 6.5.0 and Windows Server 2019.
Hi dramdin
Did you figure this one out? I don't have any physical servers to test on.
Could I ask what image you are using when installing?
Hi,
I'm having the same problem and I have used the latest build on the ISO from Microsoft and installed both Windows Server 2019 Standard and Datacenter with the same result.
"Windows created a temporary paging file..."
Versions:
VMware ESXi, 6.5.0, 8294253 and SW_DVD9_Win_Server_STD_CORE_2019_64Bit_English_DC_STD_MLF_X21-96581.ISO
//MickeMeck
You folks may want to open an SR with VMware on this one since Server 2019 was just released and also support for that was just qualified to 6.5+. This may be a known issue, but raising an SR helps push it through.
Hi Kristian,
I ended up opening a Premier support ticket with Microsoft and they confirmed that it is a known bug with Server 2019. They don't have an ETA for a hotfix yet but I will reply back when I know more.
I actually got it working, using a SATA controller disk for the pagefile.
System disk can run anything as long as the PF disk is SATA.
Looks like the issue is resolved in the november/december CU for Windows Server 2019.
Installed and cannot reproduce anymore.
The release notes for the Nov/Dec CU dont mention anything about this issue. Do you have a specific KB Number?
Tried it with latest updates installed but the problem stays the same.
The December cumulative update did not fix the issue for me either.
Looks like the problem is back for me as well...
Latest patch installed today and it's back.
Have been running fine with December CU.
/Kristian
Hello Dramdin, Any news on this?
We're having the same issue described in this thread.
I've installed the January 2019 patches but the problem persists, so it doesn't appear to be resolved with the latest fixes.
The preview of the February updates is out on Wednesday, so I'll try again then and report back.
I've carried out some further testing and tried the below patch levels and had the issue in all cases using the PVSCSI controller
Vanilla 2019 install from X21-96581 ISO
Above with 2018-11 Cumulative Update for Windows Server 2019 for x64-based Systems (KB4467708)
Above with 2018-11 Cumulative Update for Windows Server 2019 for x64-based Systems (KB4469342)
I also spooled up a Windows 10 - 1809 VM, and have the same issue, so at least it appears to be broken on both server and desktop branches of the 1809 build.
I've checked for preview patches and it doesn't look like these exist for 2016 and above.
LittleCrow,
I can confirm a similar problem here too.
I found this thread looking for answers on my problem as well.
Windows 10 1809 & Windows 10 1809 LTSC both have this problem for me when generating linked clones.
Also, Windows 10 1803 had this problem after I updated to the KB4480976 on Jan 16th after they released a 2nd cumulative update for 1803.
I was able to resolve by reverting back to KB4480966 that came out on Jan 6th.
Microsoft support just let me know that the issue has been addressed in KB4476976. I installed it on my test server and can confirm that it is indeed fixed.
It's listed in the notes as:
Addresses an issue that occurs if you create a page file on a drive with FILE_PORTABLE_DEVICE characteristics. The “Windows created a temporary warning” message appears.
https://support.microsoft.com/en-ca/help/4476976/windows-10-update-kb4476976
Was just going to post exactly that.
Checked our patch management system this morning and deployed it to a test box, and the issue is resolved.
Going to wait until it's released in the February 'B' Week to approve for all, but at least now there is assurance a fix exists.
Cheers for the posts guys, I encountered this bug while testing 2019 Core - but of course, no error message.
It took testing it with a GUI to get an error message and find this thread to realise it was a bug and not a broken script.
I'm getting this same error message on Enterprise 1803 linked-clones, but I'm not able to install the Jan 22nd update KB4476976, because it tells me it's not applicable (I assume because it's for version 1809). The last update installed was the Jan 15th KB4480976.
Is there a patch for this for 1803?
Looks like VMware doesn't have solution yet, but there is work around.
Modify your VMware Tools installation and uninstall Volume Shadow Copy Service Support component. Afer that open Windows Services and set Volume Shadow Copy server to automatic and start the service. You should be able to create a snapshot now.
Amar