I think its a Adobe bug, not a Microsoft bug. The behaviour started when Microsoft released a update (KB2993651) back in august 2014. The first thought is that it is a Microsoft issue but the KB clearly states a change in FONT behavior. Adobe didn't react to this change and Microsoft keeps updating the engine on a monthly basis so there are already alot of other KB's that can cause the same issue. Furthermore. The same problem already existed before in 2011 on older systems. Adobe never figured it out and only suggested a workarround. Acrobat/Reader: Z@xxx.tmp files left behind in Temp folder after printing Another user on this forum did some research and found that Adobe uses a legacy function when printing from Adobe reader. http://blog.notmyfault.ch/?p=378 If Adobe leaves Z@ temp files behind in the user temp directory after printing and those files can't be deleted other than a reboot it must be a Adobe bug. Other utilities like FoxIT reader do not have this problem on modern updated Windows OS-es. ... View more

OS: Server 2008R2 (two machines) In my case the issue stil exists with the new Adobe acrobat Reader DC. (Only have KB2976897 installed) ... View more

After dealing with this annoying issue a few months ago in october it came back to haunt me once again.. The earlier fix was to uninstall KB2993651 and decline the update through Windows Update or WSUS. That worked for us. That worked fine until last week when we had to perform a Windows Update cycle for other security related issues. After that update cycle we are seeing the z@ tmp files again on both our terminal servers (Server 2008R2, no citrix ) I've searched in my "installed updates" for all mentioned updates in this topic and found only 1 update mentioned here. In our case update KB2976897 which i'm going to uninstall later on. We've also updated Adobe reader X to Adobe Reader DC (build 15.007.20033) but this newest edition does not solve the underlying issue. I don't have enough time to search if the newest build of Adobe Reader DC still uses the old "CreateScalableFontResource" function as mentioned by MichaelvK83. If so it will be very unlikely that Adobe is going to fix their issue... I can blame Microsoft for a lot of bad things happened to Windows updates recently but this isn't one of them. This is purely a Adobe issue going strong for years.. I'm so fed up with this I’m going to implement the workarround for redirecting %tmp% to another location. ... View more