Hotfix Update: Parallels Desktop 4.0 Build 3540 is available

I don't believe this is a Microsoft issue though. My Vista installation through bootcamp works perfectly. I see other posts in here about the control panel issue which only happens when I use PD4.
 
The same here. I applied the hotfix, run Vista Repair in native bootcamp...
Still no results...
Vista repair says everything is fine.
In Parallels bootcamp i don't have a control panel... (and printing etc..)

Is there a way to remove alle parallels stuff from my windows partition and
re-create a new bootcamp virtual machine?? Perhaps this is a possible solution..
 
Startup with my Boot Camp. And restart with Vista DVD.
Ran repair and it said everything is fine.
Uninstall Parallels Tools in Boot Camp.
Restart to Mac partition and launch Parallels.
Reinstall Parallels Tools

Previously, when I open Control Panel, the window opened and closed immediately.
Now, Control Panel window opened and nothing inside.

Sigh...
 
I cannot start Parallels Desktop V4 Build: 3540.. I get the following error all the time no matter what i do.


Unable to connect to Parallels Service.

Make sure that prl_disp_service is running or check your firewall settings. If the problem persists, contact the Parallels support team for assistance.
 
Last edited:
Not a microsoft issue

I cant believe that support is suggesting that this is a ms issue, Boot camp vista works perfectly, Parallels 4.0 was the catalyst for the issues that everyone is talking about.

There remains no way to use 4.0 because tools wil not install

I have now removed 4.0 and will reinstall 3.0 , it has been a enormous waste of time,

Peter

[email protected]
 
I tried to go back to 3.0 and now it wont let me install because it says i need to remove parallels server or it wont run the installer
Help??????!!!! what does that mean and how do i do a clean install of p3.0, i have the original file for 3.0 but it wont run
 
Windows XP DPI setting can not be changed

in Control Panel -> Display -> Settings -> Advanced -> General :

DPI setting is always 96 dpi (normal size). Making any other settings has no effect. It seems this problem arises after Parallels Tools are install.
 
3540 doesn't fix my problem - Error 1935 see details

I had previously contacted support who told me to upgrade to build 3540. Once I did that still had the same problem which is. I install Parallel Tools it gets right up to the end where it says Publishing product information and comes up with an error box that says:

Error 1935. An error occured during the installation of assembly component {98CB24AD-52FB-DB5F-A01F-C9B3B9A1E18E} HRESULT: 0x080070057. If I reboot the box without clicking that a hobbled copy remains. if I hit ok it backs out the whole install.

I've been using 3.x since 3.x came out just fine so this not an issue of my MAC not being able to run parallels.

Hank

Andrew @ Parallels said:
Dear Users,

Parallels Desktop 4.0 Build 3540 is available for download:
http://www.parallels.com/download/desktop/

IMPORTANT! - This is English build and won't work with localized activation keys. Localized builds will be available soon.

Bugfixes and improvements:

Improvements in the upgrade procedure:
- BSOD in Boot Camp with the "Autochk not found" message followed by the session manager crash - fixed.
Note: If you see this BSOD in the release version of Parallels Desktop 4.0, open the virtual machine configuration, select Hard Disk 1 in left pane and click OK. This will prevent this BSOD in the virtual machine and the Boot Camp partition.
- BSOD with the "0xA5" message during the virtual machine upgrade - fixed.
Note: If you get this BSOD in the release version of Parallels Desktop 4.0, convert the backup copy of your virtual machine. Before convering the copy create one more backup copy of it.
- Windows stops on boot during the upgrade without any crashes - fixed.
Note: If this error occurs in the release version of Parallels Desktop 4.0, convert the backup copy of your virtual machine. Before convering the copy, create one more backup copy of it. Alternatively, you may add the "vm.compat_level=2" string to Virtual Machine Configuration > CPU > System Flags (make sure that the "show advanced settings" option is selected).
- Virtual machine crashes on start after the conversion - fixed.
- Possible causes of BSOD in intelppm.sys and agp440.sys - fixed.
- Mouse is not available when upgrading a virtual machine that was originally created with Microsoft Virtual PC - fixed.
- The sound is disabled in Windows XP virtual machines after the upgrade - fixed.
- Hard disk cannot use the Boot Camp partition after the upgrade - fixed.
Note: If this error occurs in the release version of Parallels Desktop 4.0, open the virtual machine configuration, select Hard Disk 1 in left pane and click OK.
- The message "Failed to configure the Boot Camp partition" appears after the upgrade - fixed.
Note: If this error occurs in the release version of Parallels Desktop 4.0, open the virtual machine configuration and click OK.

Other improvements:
- At times Parallels networking drivers don't start after the restart of Mac OS X - fixed.
- Copy-paste operations may fail in some cases when the virtual machine is in Coherence - fixed.
- Copy-paste operations may fail in some cases when non-text data is being copied to Windows - fixed.
- Inability to switch to a Windows application using Application Switcher when the virtual machine is in Coherence - fixed.
- Redundant network icons appear in the Mac OS menubar after switching between the view modes - fixed.
- Mac applications stay on top of Windows applications in Coherence - fixed.
- USB performance improved, including the ability to sync iPhone with iTunes installed in Windows.
- Dispatcher service binding to all network addresses on port TCP 64000 - fixed.
- The ability to suspend a Boot Camp virtual machine was removed, because this operation may damage the Boot Camp partition.
- .NET applications menus drawing in Coherence - improved.
- Crashes in virtual machine monitor and the application based on the statistics received through the problem reports - fixed.

Known issues:

- A message "hal.dll is missing or corrupt" may appear when you use the Boot Camp partition natively if the Boot Camp virtual machine was shut down incorrectly in Parallels Desktop 3.0. To toubleshoot this issue, edit the boot.ini file to be able to log in with a proper user profile.
- Removing the virtual hard disk from the virtual machine configuration and then adding it again results in moving the hard disk to the last position in the virtual machine's boot order, which seriously increases the boot time. To troubleshoot this issue, edit the boot order in the virtual machine configuration after readding the virtual hard disk.
- Control Panel may be unaccessible in Windows Vista loaded from Boot Camp.
- Scheduled chkdsk may fail to start on Windows Vista booting in a virtual machine.
- Parallels Desktop may start consuming up to 100% CPU after setting 2 CPUs in a Windows virtual machine configuration. To troubleshoot this issue, update the CPU driver in the Windows guest OS.
- A Windows Vista Boot Camp virtual machine may request to be activated again after upgrading to Parallels Desktop 4.0.
- The maximized window of a Windows application may cover Windows taskbar in Windows virtual machines that were converted from Parallels Desktop 3.0 format. To troubleshoot this issue, right-click the Windows taskbar, select Properties and enable the "Keep the taskbar on top of other windows" option.
- All guest operating system windows are minimized after switching to another Space. To troubleshoot this issue, switch the virtual machine to the Window mode and then back to Coherence.
- The virtual machine will not change its IP address after switching from the bridged wired to wireless network and vice versa, which may result in the virtual machine's disconnection from the network. To troubleshoot this issue, right-click the networking icon in the guest Windows operating system and click Repair.
- The Parallels service user profile may remain in a Windows virtual machine after the upgrade to Parallels Desktop 4.0 is complete.
- Parallels Transporter and Parallels Mounter are unable to work with Boot Camp partitions.
- You cannot revert to snapshots that were created on 32-bit Mac host computers and resume virtual machines that were suspended on 32-bit host computers with Parallels Desktop installed on 64-bit Mac OS host computers, and vice versa.
Click to expand...
 
How exactly do you "update CPU driver in Windows OS"? I tried searching for new hardware and it found nothing,

PS> Please excuse my prior nonsensical accidental entry.
 
Unless you work for Parallels davert please don't ever tell me how to post my comments again. I'll post them how I want, you post yours how you want.
 
Hyeomans -
You seem to want to make trouble.
My mistake was posting Post Quick Reply, and the default text got up there.
You want to start a fight? Go pick on someone in a bar.
 
Thank You, you made it!

John@Parallels said:
JoOppen
You can attach old disk to new VM, and retrieve data

bblitzmu
If it is Windows Vista
Please perform Windows Vista repair and install build 3540
Click to expand...

John, Andrew, Evgeny et al.

You have solved my BSOD A5 problem. The link to http://kb.parallels.com/en/5774 was very helpfull.

Retrieval of data by creating a new VM and attaching the old HD to the new VM is also very helpfull, in particular if your old VM is a bit messy.

I have tried both ways know and both worked for me.

Thank you for your support it is realy helpfull!

JoOppen
 
Back to 3.0, how to reinstall sucessfully , tip!

I decided to stop waiting for p4 support to solve the 1306 problem ( they have no idea) so i deleted 4.0 vm and went back and installed 3.0. I would caution anyone upgrading a boot camp disk that tools installation may not work

Going back to p3 got me into more trouble as p3 would not install , it kept giving me an error about "cannot install please stop parallel server"

if you decide to go back, you must uninstall p4 from the proper p4 uninstall dialogue or it wont remove p4 fully and you wont be able to revert to p3.

I now have p3 working again, ( my computer is back to where it was a week ago) and tools installed perfectly

Now ive wasted a week and spent $50.00. Im not sure what to do next, Ill probably look to get my money back or wait for a fix?

Im not impressed

Peter
 
>IMPORTANT! - This is English build and won't work with localized activation keys. Localized builds will be available soon.

What does this mean in plain english? What's a "localised activation key"?

Should I risk installing this build or not?
 
Since Parallels makes changes to the startup - and possible a kernel extension - I'd certainly expect to have to do a full uninstall before regressing. (Though I'd consider P4 to be a severe regression in a lot of ways! Like now, Windows can draw enough processor power from Mac OS that I can't leave it run in the background and expect to type properly, even just using two out of four cores).

I believe what they mean is that if you use a language other than English, it won't work.
 
tblack

Honestly, i would wait before upgrading, tech support is lost on many of the issues. I would just hold off for a bit unless you have lots of time on your hands.
IMHO ....dont upgrade.
Maybe someone else here will provide a positive response?
Peter
 
You must log in or register to reply here.
Back
Top