The telling sign would be if the behavior persists across reboots. If a reboot doesn't make the error go away, then it's not anything UPHClean is going to fix. I had this same problem some time ago and the answer was indeed to twiddle the PagedPoolSize and PoolUsageMaximum. If that doesn't work, I'm stuck. ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk Sent: Tuesday, October 26, 2004 8:28 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Windows cannot load your profile. Please increase the registry size and restart the computer. Download and install UPHClean from the Microsoft web site. This could due to profile not unloading properly and stealing system resources. Joe ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Nuno Jose Sequeira Sent: Tuesday, October 26, 2004 5:00 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Windows cannot load your profile. Please increase the registry size and restart the computer. Our customer is having problems with their Citrix servers: 4 Citrix MTF XPe FR3 servers w/ 60 users (1 server with 4Gb RAM, 1 with 1,5Gb, another with 1Gb and the last one with 700MB) They are getting this error ID: 1000 Windows cannot load your profile. Please increase the registry size and restart the computer. Windows cannot log you on because the profile cannot be loaded. Contact your network administrator. DETAIL- Insufficient system resources exist to complete the requested service. I've used many Microsoft's advices like: http://support.microsoft.com/kb/312362/EN-US/ And setup the registry on ALL the servers like: RegistrySizeLimit = 256Mb AND Value name: PoolUsageMaximum Data type: REG_DWORD Radix: Decimal Value data: 40 Setting the value at 40 informs the Memory Manager to start the trimming process at 40 percent of PagedPoolMax rather than the default setting of 80 percent. Value name: PagedPoolSize Data type: REG_DWORD Radix: Hex Value data: 0xFFFFFFFF Setting PagedPoolSize to 0xFFFFFFFF allocates the maximum paged pool in lieu of other resources to the computer. This setting consumes a lot of Page Swap, and I've also found out that we are still having the same MSG error mainly on the 4Gb RAM server and on the 1.5Gb RAM! Could you please help us? This is becoming critical and users cannot login to the servers!!! Thanks. Regards, Nuno