SANCHAI  Version 2.8.6 released today crashed when startup under Snow Leoprad 10.6.2. Version 2.8.5 work fine. Help please  
(Version 2.8.6)

SANCHAI  Adobe Acrobat Pro 9.2 update fail to upgrade 9.1.3 to 9.2 properly. Same failure as mentioned above.

The error dialog read "Update failed. The patch has failed because the application has been modified since it was originally installed (for example, plug-ins may have been disabled). Please go to the Adobe support website for more information regarding how to re-enable disabled components prior to installing the patch. Or, you can install and reinstall the application, and then reinstall the patch."

Adobe Reader update to 9.2 run fine. I have seen this failure in many places around the net. Caome on Adobe here you go again. New update that work please!  
(Version 9.2)

SANCHAI  Adobe Acrobat Pro 9.2 update fail to upgrade 9.1.3 to 9.2 properly. Same failure as mentioned above.

The error dialog read "Update failed. The patch has failed because the application has been modified since it was originally installed (for example, plug-ins may have been disabled). Please go to the Adobe support website for more information regarding how to re-enable disabled components prior to installing the patch. Or, you can install and reinstall the application, and then reinstall the patch."

Adobe Reader update to 9.2 run fine. I have seen this failure in many places around the net. Caome on Adobe here you go again. New update that work please!  
(Version 9.2)

SANCHAI  Adobe Acrobat Reade upgrade fine to 9.2 but Acrobat Pro9.1.3 update to 9.2 fail due tot the same error mentioned above. Again Adobe problem!!!  
(Version 9.2)

SANCHAI  Same here. Just cannot upgrade to 9.2 because the same thing you mentioned  
(Version 9.2)

SANCHAI  This is my support request to parallels!!!

I have upgraded from parallels 4.0.3844 to the new build 4.0.3846 when my OS was 10.5.8. After many crashes when attempting to install Parallels Tools to WIndows, I managed to get Parallels 4.0.3846 installed on my system.

After installation, I tested run WIndows under parallels, it work. But when I shut down mac OSX 10.5.58, reboot, press Option key and select to boot into Windows directly from Bootcamp (not via Paralles), the problem started.

At boot, Chkdsk run to check dist consistency and found error in index (details similar to one I will show later). I wait for Chkdsk to finished, reboot, press Option key, then boot into Windiws. This time the boot is fine and my Windows Vista run OK.

At this point, I thought that there is no problem, and proceed to upgrade to Snow Leopard (10.6). the upgrade process is fine. Windows run under Parallels fine. But when I shut down Mac OSX, reboot, press Option key, then boot intoWindows, the same problem occurred. Chkdsk run every time!!!

Whenever I used Mac OS, shut down, then restart the WIndows Vista by pressing Option key at Macbook Pro startup, Chkdsk will run every time, checking integrity of the Windows boot partition. I have to wait for more than 20 minutes before Chkdsk fix all errors, then reboot, and press Options key to get back into Windows Vista without Chkdsk running.

When I shut down Windows, and restart without going into Snow Leoprad, the boot process go OK without Chkdsk running.

But whenever I shut down Winodws and use Snow Leopard (whether or not parallels is used), then get back in to startup Windows, Chkdsk run again. This is very annoying, and never occured in the previous build 4.0.3844

During Chkdsk session, the following errors occured and being fixed:

Deleting index entry ._501 in index $I30 of file 9028

Deleting index entry 501 in index $I30 of file 9028

and after all process finished, Chkdsk stated that: There is a blank space that allocated as used, and has been fixed.

The problem is repeatable. The same index and file to be deleted by Chkdsk remain unchanged every time I boot Windows under bootcamp after using Mac OS. If I reboot Windows many many times without using Mac OS, the error never occur.

I remembered that Parallels 4.0 initial build also have this kind of problem. After upgrade from 3.0 to 4.0, Chkdsk won't run at startup when it had been scheduled. I reported support ticket to Parallels at that time, and the problem had been fixed in later build.

I'm very confident that it's Parallels 4.0.3846 that cause this problem? and How to correct it?

I suspected that parallels alter disk in WIndows Vista that cause Chkdsk to run when startup in bottcamp. When I start WIndows in Parallels 4.0.3846 under Snow Leopard, the startup is OK

Help me solve this problem, and respond please!!!! I wasted too much time with Parallels already. I'm very loyal to Parallels. So don't let me down. I want explanation and solution!!!! Please get back to me soonest.

Thank in advance for support  
(Version 4.0.3846)

SANCHAI  Failed Parallels Tools installation from Parallels Desktop make disk error in Windows partition (MFT errors). This problem resulted from crashes of the installatyion of Paralles Tools.

What I have to do is to run chsdsk /f to fix error. And it took me another hour for the chkdsk to finished.

Thank you Parallels for releasing buggy software all the times. I'm so glad I paid for Paralles!  
(Version 4.0.3846)

SANCHAI  Yes, I have a nightmare in upgrading Parralels 4.0 build 3844 to this new built 3846. The problem is crash when my Vista SP2 on bootcamp partition started in Parallels. A number of blue screen of death ocuured when booting.

It took me 5 attempts that took me 4 hours before I managed to get Parallels Tools installed on my Vista SP2 bootcamp partition. The process to update Parallels Tools took more than one hour.

And after completing the installation of Parallels Tools, the startup of Windows under Parallels seems not very stable. It crash sometimes.

It always be a nightmare to upgrade Parallels Desktop!!! This happen to me many many times since version 3. May be it's a time to ditch both Windows and Parallels out of my MacBook Pro!!!

Be careful and patient for the upgrade. I warn you!!!  
(Version 4.0.3846)