.dll problems after upgrading from 6 to 7

Discussion in 'Installation and Configuration of Parallels Desktop' started by jgcms232, Jan 15, 2012.

  1. jgcms232

    jgcms232 Bit poster

    Messages:
    2
    Hello,

    I really need some help with this problem so thank you in advance.

    After I upgraded from Parallels 6 to 7 I have had the following problems.
    Please note: the programs worked perfectly before the upgrade.

    Adobe Premiere wont run and gets the following errors:

    C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_a4d6a923711520a9\comctl32.dll is either not designed to run on windows or it contains an error


    Pinnacle Studio HD Ultimate 15 has the following problem:
    The preview screen will not render previews:

    I have 16 GIG of Ram in my MAC and Parallels only detects 8 GIGS

    I would love some help on this:
    Thank you
    Jeff
     
  2. Specimen

    Specimen Product Expert

    Messages:
    3,236
    The maximum RAM you can assign to a VM is 8 GB (this limitation already existed on PDM 6).

    I suggest you uninstall Parallels Tools from control panel>add remove programs, reboot the VM and install Parallels Tools again, and see if it solves the problem.
     
  3. jgcms232

    jgcms232 Bit poster

    Messages:
    2
    I will try this.
    my comctl32.dll is corrupt and so I want to replace it if this does not work. Is there a way I can access
    c:\windows\System32\ files from my mac without starting the VM? I can not seem to figure out how to do this.

    Thanks
    Jeff
     
  4. Specimen

    Specimen Product Expert

    Messages:
    3,236
    Find your VM .pvm file right-click on it and select Open With > Parallels Mounter (or similar wording), it will mount the volume on your desktop.

    The correct procedure for dealing with system files corruption is using the Windows installation media and running Recovery Console and/or Repair Install. For more information on this consult Microsoft's documentation.

    I advise against replacing the file, more than likely the file is NOT corrupted, you should run chkdsk via the Recovery Console, and use Windows own tools to deal with Windows system files.
    Also, be aware, that there you'll find many .dlls (and other files) in your system folders that have the same name, these are different versions of the file that got upgraded. Replacing a system file should be done using the exact same version of the file being replaced.
     
    Last edited: Jan 15, 2012

Share This Page