Login takes over 10 minutes (or longer) with sharing enabled...

Carson_Wilson

Bit poster
...previously, I would get a warning message stating something along the lines of my shared folders being remapped and I had to reboot (this would happen over and over). There was a registry fix for that that I applied that seemed to be ok for a while.

However, now it's started again but worse. In the past, it took around 10-15 minutes to log in. Now, it just never logs in. If I turn off all sharing it logs in immediately no problem.

I have tried turning off sharing, uninstalling Parallels tools, reinstalling Parallels tools, turning on sharing (with reboots inbetween) with no luck. I tried applying the registry fix again, and this time it worked!

Aside from this, everything with Parallels works flawlessly. I did have to do a windows update, and that is when the problem occurred. Is it possible it removed the registry entries?

More importantly, is there going to be a fix for this issue going forward so I won't have to keep re-applying the keys?

FYI I am using Yosemite, Parallels 10, and Windows 7 Ultimate. Thanks!

Carson.
 
It turns out that every time I reboot, this occurs. I have to shut off sharing, reboot, apply reg fix, turn on sharing, reboot.

This is frustrating - any insight on this would be appreciated (a fix, an acknowledgement of a bug that will be fix, some indication of something wrong on my side that I need to change etc.).
 
Hello Carson,

Please follow the steps provided below:

1. Open virtual machine Configuration (http://kb.parallels.com/117287) - Options tab - Sharing - turn OFF 'Shared Profile' feature.
2. Start virtual machine - open Windows File Explorer and go to : C:\Program Files (x86)\Parallels\Parallels Tools
3. Rename prl_uprof.dll to prl_uprof_old.dll
4. Restart virtual machine.
5. Open virtual machine Configuration (http://kb.parallels.com/117287) - Options tab - Sharing - turn ON 'Shared Profile' feature.
6. Download Shared Profile from http://kb.parallels.com/Attachments/kcs-34079/sp_correct.reg and run it.
7. Restart virtual machine.
 
Back
Top