Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About supjack

Profile Information

  • OS
    Windows 7 x64
  1. <br /><br />even with this setting applied?<br /><br /><br /><br />Yes, right now I have two Win 7 guest OS installs on top of ESX 4.0, I also have 4 physical Win 7 installs (3 are new laptops). All of the Win 7 installs are domain members. Not one of the users of these systems has complained about shut down time so I checked to see the shut down time myself when I noticed things with this particular one. They do not shut down fast but the seemed to be not too bad, I guess thats why no one complained. The XP boxes (about 40 of them), that are on the same domain that are effected by the same policy seem to shut down pretty quickly.
  2. <br /><br /><br />Its a domain security policy setting pushed to the member PC's. At some point someone here checked off this setting, or the setting was included within a security script run against the server to tighten things down. The domain controller is so old I'm not exactly why or exactly when this was done. No real negative effect on the XP boxes though so I guess until now its been a non issue. Still weird that on two other Win 7 boxes the shut down is not too bad (about 60 seconds). With the box in question, I've timed at about 13-14 minutes a couple of times.
  3. Update on my issue While working with MS support I found that if the value for ClearPageFileAtShutdown is 0 then the shutdown is speedy. It seems that this value is given via a domain policy setting. On the physical Win 7 PC's and the one other virtual Win 7 PC's (and all of the Win XP PC's) you can see this setting causes a little more time (slight) to shutdown. On the this particular Win 7 PC (virtual running on vmware), if I edit the ClearPageFileAtShutdown value from 1 to 0, the shutdown process seems to be fixed. However I did notice that if I added or removed software the setting reverts back to 1. So at this point I'm closer to finding solution but its not 100%. I may just stop at this since we are trying to get a Win 2008 domain controller online to replace the the Win 2000 domain controller and the issue may not get fully addressed till the 2000 server is out of the picture. What I would like to understand in the mean time are the following entries found in the same location as the ClearPageFileAtShutdown reg key. On 2 WinXP machines that I checked, there's two entries that look like the following: ExistingPageFiles.......REG_MULTI_SZ....C:\pagefile.sys 1524 3048 PagingFiles.............REG_MULTI_SZ....C:\pagefile.sys 768 1536 On the Win 7 machines that I checked (1 phy & 1 virt) these show as: ExistingPageFiles.......REG_MULTI_SZ....\??\C:\pagefile.sys PagingFiles.............REG_MULTI_SZ....?\C:\pagefile.sys MS support has not responded yet about the syntax of the values above. It may be that I'm missing something obvious.
  4. Yes for now we have a Win 2000 domain. We have a couple of Win 7 boxes running without this problem. Trying to move to Win 2008 SBS but we have issues with the changes MS made with how things work with Unix. Were not using a sophisticated file sharing setup here, or a sophisticated active directory. It used to be that we could just use simple mapping via the services for Unix application to allow a couple of accounts on the Unix system to put files out on the shared drives. MS has changed things in that it now requires a more detailed and in depth server configuration and network setup to play nice with Unix. I'm going to try and just muck with the system on my own today to see if I can figure out why after adding to the domain that the system changes with regards to hibernation. I'm thinking that I may use a sysinternals utility to watch what gets changed on the machine when added to the domain. I have confirmed that I can remove it from the domain and the shut down issue goes away, and then comes back again after again adding it.
  5. MS paid support will not help fix until we upgrade the domain controller. They went through everything I did all over again to confirm that the issue is after adding the PC to the domain. Its not third party software or user tweaks after the install. Something with the add of the PC to the domain makes a change in the PC so that it now looks for a hybernation.sys file which does not exist so it just sits and spins. The over all feeling that I got as a result of the time spent with MS support was that once they had a BAILOUT they took it. I my gut tells me that an upper level tech more or less told the person I was working directly with that its a $$ loser support call due to the need to get deeper into things and to just dump it and move on over to another support request in the queue.........being that Win 2000 is no longer supported thats the BAILOUT. I doubt its an issue with Win 2000 because we have a couple of physical and virtual Win 7's working on the domain.
  6. Will do, am filling out the request for MS support web form on the support.microsoft.com now.
  7. I'll be calling and paying for MS support to look this into today. One thing I did notice about this is that the issue creeps up after adding the PC to the domain. However once you add the PC to the domain MS will not help resolve anything without agreeing to pay a per incident fee or having an business support contract, free installation support is available for the OS as long as the OS has not been setup as a member of a domain.
  8. ran powercfg -h off from elevated command prompt..........seemed hung at first, but maybe it was busy dumping the hyberfil file. Tested by doing two re-boots...............seems like nothing changed EDIT 1: Have removed all software and the same things is still there after each item removed . Going to wipe and start over and what closely for the issue after each little change is done to see if I can catch what caused the issue. My guess right now is that something got tweaked during a software install and the Windows removal process has not backed it out. <br /><br />Also, vmware initially wanted me to apply <a href='http://www.microsoft.com/downloads/details.aspx?FamilyID=3a7b7298-37e6-4edf-a017-09a6bbc75287&DisplayLang=en' class='bbc_url' title='External link' rel='nofollow'>http://www.microsoft...&DisplayLang=en</a> But it does not specifically say its for Win 7 systems as well so I did not try it. EDIT 2: dumped trying to fix the existing install, figuring that its going to be like chasing a ghost to fix it. I did fresh install and let the process auto update with two patches KB978601 & KB979309. As part of the install process the system rebooted. This was lighting quick. After the re-boot, to check and insure, I manually rebooted the system, it went through the shut down process lightning quick. Executed the vmware tools install "setup64.exe" from within the guest and left the default options as selected. The install process initiated re-boot at the end, again the system re-booted lightening quick. After coming back up, to check and insure, I manually rebooted the system, again it went through the shut down process lightning quick. I then went through the process to add the PC to the domain. Slightly slower re-boot this time. The boot up process took a little longer this time to get to a CTRL-ALT-DELETE. Logged in as domain administrator, once the desktop came up, I re-booted. OK, the long time to shut down is now happening again. Once it finally re-booted I logged in as another user and then did a re-boot.......again same thing. I'm wondering what can change within a basic Win 7 OS install after adding a PC to a domain, and a user logging in for the first time........this is a real basic Win 7 OS install. We do not use log in scripts or sophisticated domain policies.........its a real basic setup in order to keep things simple to work with and maintain. So far we have three other Win 7 installs including one that's virtualized like this one, no issues with them. Andre, I'll get another file over to you from this fresh install.
  9. I'm creating a ticket with vmware support right now because my gut tells me at this point that the vmware tools install could be the only thing thats been installed so far that could tweak things like this. I've also been looking power and performance setting in Win 7 but I need to review things first, MS has changed the interface so much I'm seeing that I need to re-learn things as well as finding where the gui interfaces to sub components are now located.
  10. <br /><br /><br />This PC's only function was to be for a user to work with QuickBooks 2010 so all that was installed was: Vmware tools (the PC is a guest on top of ESX 4.0 host) QuickBooks 2010 Windows performance tool kit (installed for this issue) BillP Winpatrol (installed for this issue) F-Prot Anti-Virus And a registry mod from this link found here when selecting the download button. But I got this and ran it after having the issue in question. http://www.sevenforums.com/tutorials/26476-desktop-shutdown-tweaks-combined.html Thanks for looking at this
  11. Hello I have a fresh install of Window 7 x64 thats a guest on a vmware ESX 4 host. Windows 7 has been patched and has QB 2010 installed. A couple of other smaller supporting apps have also been installed but basically the PC is just to be used for QB. Shut down is problematic and takes for ever. I did some searching via Google and came across this thread. I've followed the the information for installing the MS tool to create a trace of whats going on in the system and I opened the files to see if I could find the issue without posting linking the file here. However after looking at the program I realize I'm not savvy enough to look through the displayed information and determine what is the root cause of my issue. Now my issue is getting the files out there on the internet so someone here can look at it and then assist hopefully me. The problem is that I'm not 100% sure I want this information out in the public as I'm unsure what can be gleamed from what I put out there to put the PC or the network its on in jeopardy. Can someone post up some more details about the contents of files and on making them public? Also, do not have LiveID or a Rapidshare account. I can open an account on Rapid share but I did not want to do unless I was more comfortable with the this.
  • Create New...