Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Legacy Products > Pro Tools 10

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 10-02-2022, 04:36 AM
BinaryAlchemist BinaryAlchemist is offline
Member
 
Join Date: Oct 2022
Location: Severna Park
Posts: 1
Default Pro Tools 10 on Windows 10

I've got an old but much loved copy of Pro Tools 10. When I was finally forced to upgrade from Windows 7 to Windows 10, though, I had issues running it. I finally got it (mostly) running last night and figured I'd post the steps I took here in case it helps someone else out. As always, YMMV.

Before you do anything else, create a Restore Point in Windows. You may also want to do a complete backup if possible. My computer got borked up several times along the way and I had to restore from Restore Points.

The first issue I encountered was that the old iLok driver was causing Windows 10 to crash on startup. This is the dreaded "page fault in nonpaged area" BSOD issue from tkpd.sys. It turns out that the old iLok driver used a Windows feature (interactive services) that Microsoft discontinued and PACE never released an update to account for that:

http://duc.avid.com/showthread.php?t=411117&page=3

One option people suggested was to roll back Windows 10 to version 1909. That wasn't an option for me. Instead, I bought a new iLok. I then used VirtualBox to create a Windows 7 VM, plugged in both iLok devices, and moved my licenses to the new one.

I then downloaded Pro Tools 10.3.10 from Avid:
https://avid.secure.force.com/pkb/ar...3-10-Downloads

There was some fumbling here, so if someone else tries these instructions maybe they can refine them. But I believe at this point, I ran "setup.exe" from within the "Pro Tools Installer" subdirectory to install Pro Tools while bypassing the PACE iLok installer that tries to set up the old (buggy) tkpd.sys driver.

Pro Tools then appeared to install successfully. However, when I ran it all I got was a quick splash screen and a crash. When I looked in Windows Event Viewer, I saw the following:

Quote:
Activation context generation failed for "c:\Program Files (x86)\Avid\Pro Tools\ProTools.dll".Error in manifest or policy file "c:\Program Files (x86)\Avid\Pro Tools\Microsoft.VC80.MFC.MANIFEST" on line 5. Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC80.MFC,processorArchitecture="x86",pub licKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="8.0.50727.6195". Definition is policy.8.0.Microsoft.VC80.MFC,processorArchitectur e="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="wi n32-policy",version="8.0.50727.762". Please use sxstrace.exe for detailed diagnosis.
This is an issue with Microsoft's "Side-by-Side" ("SxS") system that was supposed to save us all from so-called "DLL-hell", the situation you get yourself in when two programs on your computer need two different versions of the same shared library. In this case, it's the Visual C++ 8.0 runtime libraries for x86.

There was quite a bit of fumbling here, too, and I ended up downloading and installing this update although I'm not sure it was necessary:

https://www.microsoft.com/en-us/down....aspx?id=26347

It would be the "vcredist_x86.exe" version if you need it (since Pro Tools 10 is a 32-bit app).

Installing that, unfortunately, did not solve my problem. Next, I went looking for the specific DLL that Pro Tools was searching for. I ultimately found it here:

https://www.opendll.com/index.php?fi....0.50727.6195#

I then dropped the DLL file into "C:\Program Files (x86)\Avid\Pro Tools" hoping it would pick it up. Unfortunately, it still didn't see the DLL. Running Procmon from sysinternals, I could see that Pro Tools was looking for "Microsoft.VC80.MFC.MANIFEST" in the "C:\Program Files (x86)\Avid\Pro Tools" directory.

I rummaged around in "C:\Windows\WinSxS\Manifests" until I found one that looked like what I needed called "x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727 .6195_none_cbf5e994470a1a8f.manifest". I copied that file into "C:\Program Files (x86)\Avid\Pro Tools" and renamed it to "Microsoft.VC80.MFC.MANIFEST".

Here is the file contents in case you can't find the same manifest:
Quote:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<noInheritable></noInheritable>
<assemblyIdentity type="win32" name="Microsoft.VC80.MFC" version="8.0.50727.6195" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
<file name="mfc80.dll" hash="48ac38e27b9666515a92c5e97834d48d40764681" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>tpIBsHBROfAlpY MDRDbXYcHmLgk=</dsig:DigestValue></asmv2:hash></file>
<file name="mfc80u.dll" hash="cf19ab729dce5f8169380752f43748935e85f57d" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>oJG2Jr4nbHQujY +GmI7Qfx6Qg9Q=</dsig:DigestValue></asmv2:hash></file>
<file name="mfcm80.dll" hash="2741e9d7b38d6e6ccd1390337230a300ea3ff7c0" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>dNEbvz2oqiF9Ho NCWmdiGxJjccU=</dsig:DigestValue></asmv2:hash></file>
<file name="mfcm80u.dll" hash="11c54b3382933f03eb2d241b7933f46bed1b7b8e" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>gouNpismXZmivn Qe1U1Kt95h+DM=</dsig:DigestValue></asmv2:hash></file>
</assembly>


After that, Pro Tools started up. I ran the (new) iLok License Manager in the background logged into my account. I also found that I had to right-click Pro Tools and run it as an Administrator to avoid getting errors about insufficient privileges. Note that you can right-click the Pro Tools shortcut on the Desktop, go to "Properties", click "Advanced", and check "Run as administrator" to avoid doing this every time.

At this point, the basic program was working - I could create sessions, add tracks, record, and playback. I was also able to activate my old Guitar Rig 5 Plugin by downloading the latest version of Native Access (yay to Native Instruments for supporting legacy software!).

The one issue I still have is that I can't run any of the Avid Virtual Instrument plugins. When I try, they appear to be looking for the old iLok driver ("This software requires installation of the InterLok(R) device drivers ..."). Unfortunately, I still don't have a workaround for that. I may just have to live without those plugins. If anyone else knows of a fix or workaround please let me know.

Anyway, heck of a way to spend a Saturday. Hope all that was able to help someone else out.
Reply With Quote
  #2  
Old 04-06-2023, 06:01 AM
jyt jyt is offline
Member
 
Join Date: Oct 2005
Location: Canada
Posts: 28
Default Re: Pro Tools 10 on Windows 10

Wow, that was a hell of a good story here. I'm running an old HP XW8400 with PT 8.1.1 HD3 under Windows 7 and I'm wondering if I could just run that PT 8.1.1 but under Windows 10. I'm gonna try it anyway, I have a few SSD drives so I won't lose the current setup which run well but it's time to get rid of Windows 7. I also just purchase a Magma PEGR4 rev.B which I assume would run with my setup but got PT 8.1.1 start but as soon as it play I got DAE error -1115 then -1122, so I figure out this was perhaps the wrong Magma, this one come with the daughter card with two cable connectors x1 and x3.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Pro Tools tabbed windows in MacOs - Windows configuration not working hugocentrique macOS 3 11-06-2023 05:26 AM
Windows 11 Pro Tools still has Windows Vista style box Undead Goat Windows 13 11-17-2021 11:37 PM
Upgrade From Pro Tools LE (Windows XP) to 10 (Windows 7) miek07 Windows 3 07-26-2012 07:49 PM
Updating Pro Tools and Mbox from Windows XP to Windows 7 ryanjantz 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) 1 05-29-2011 04:22 PM
Opening a pro-tools HD session on a windows Pro-Tools LE M-powered system rhodamorgan 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) 1 09-21-2010 05:31 PM


All times are GMT -7. The time now is 11:26 AM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com