I'm running MC 7.0.3 on a surface Pro 4 with no issues until this update that just happened. Anyone have a work around? Or do I have to roll back?
MC can run on anything but not qualified for.
Using an intel HD card to run MC isn't anyway close to that.
Now if you think that the Windows 10 Cerator has done the damage you should do the rollback
and keep us updated as well.
Desktop
Asus Ζ690 TUF Gaming WiFi D4|i5 12600K|Corsair 128G DDR4|Asus 3060 12GB|Samsung 980 500GB(OS)|2X1TB Samsung 980 RAID 0|W11 Pro
Laptop
MSI Katana GF76 11UE (i7 11800H|Nvidia 3060|Crucial 64G DDR4)|W11 Pro
NLE
DR Studio 19|MC 2024.2
VDIM
r0607Ninja: I'm running MC 7.0.3 on a surface Pro 4 with no issues until this update that just happened. Anyone have a work around? Or do I have to roll back?
Hopefully, rolling back should fix your problem. For the longer term, you need to think about preventing Windows 10 from updating, which isn't as easy as it was in past versions of Windows. Ideally, you'd take your Surface Pro off the internet (which would also help prevent virus attacks), but more of us are now using our computers for multiple tasks, so this isn't always convenient.
So, your other alternative is to dive into the Policy Editor or registry settings to disable the automatic updates. Below is a link that discribes the steps involved.
https://www.windowscentral.com/how-stop-updates-installing-automatically-windows-10
Follow that rule in any case.
THanks for your help. I will have to roll back, but I do think it's silly that we still accept these issue with Media Composer. I've been running it on this machine fine for years, and other NLE's don't have these common issues.
Thanks again for your help.
r0607Ninja:I do think it's silly that we still accept these issue with Media Composer. I've been running it on this machine fine for years, and other NLE's don't have these common issues.
Sorry, but other NLEs do have "these common issues", and they also happen in the Apple world - possibly even more so there, because Apple will often enforce application changes when they issue an OS update.
If a software designer builds an application using the rules published by the OS manufacturer then those rules are arbitrarily changed, who's at fault? The app designer or the OS manufacturer? I have software that still runs on W10 that was designed and built in the 1980s. It doesn't need to do much except read and write files and rely on the OS to display the result. It will probably continue to function as long as Windows exists on Intel x86 style platforms. But it doesn't have the complexity of an NLE.
Back when I was developing software in the late '80s/early '90s this type of issue was a problem in the much simpler MS-DOS world, and it remains a problem to this day. Trust me - no developer is delighted when a driver update or OS change breaks their software. If you get frustrated, think what they must feel!
My Media Composer 7 installation suffered the same fate with the Windows 10 Creator update. I was comtemplating what to do--rollback the update, buy a newer MC, etc. But the subsequent update to Windows 10 seems to have resolved the incompatibilities introduced by the previous update. Without changes to the MC installation, it is running again! I am running Windows 10 Pro, version 1803, build 17134.48. If you are still looking for a fix, you might try going to Windows Update and installing the newest version.
I did not make any changes to MC 7.0.3 after it was disabled by the Windows 10 Creators update. But now with Windows 10 update 1803, the incompatibilities seem to be resolved and MC runs as it did before. No longer a need to rollback Windows or upgrade MC to fix the problem! I am running MC 7.0.3 on Windows 10 Pro version 1803, build 17134.48.
Anyone having issues installing 7.0.6 on Windows 10? Or Is it just 7.0.3 that will install on Win 10? I managed to install it just fine, but I'm having one heck of a time trying to get my license to work. Just gives me an error:
"There was an unspecified error (5) initialising the licensing engine"
I won't even run the 30 day trial. Previously, I ran MC 8.7 on this machine, but deactivated/moved that license to a newer PC and I wish to use this slightly older PC with MC 7.0.6 as a "B-system" for my assistant.
When I contacted Avid support the phone tech guy with a thick eastern European accent stated sort of rudely that it wasn't supported on Windows 10, then wouldn't really talk anymore. So that was that... no help for me. Hoping the nice people in this community can be more constructive Any ideas?
Jason Spencer, Director/DP/Editor
"But now with Windows 10 update 1803, the incompatibilities seem to be resolved and MC runs as it did before. "This gives me hope, but my Windows 10 is version 1709, and when I check for new updates it says there aren't any.
Edit: I just learned how to force updates that MS hasn't sent to users yet. And I'm very happy to report that upgrading to Windows 10 ver. 1809 has fixed whatever issues were causing Media Composer to crash. So I'm working on a Surface Pro 4 8GB Ram running MC 7.07 on Windows 10 ver 1809. And It's running very well.
Thanks to the user who posted this update, and thanks to auto-email for letting me know!
Hello
Look for the following folder. If found, delete the entire folder.
C:\ProgramData\Avid\Licenses
If found, delete the entire folder.
Important: If you can’t find the specific folder in Windows, go to Folder Options in the Tools menu and select “Show Hidden Folders.”
marianna
[email protected]
Marianna... you are the greatest. Deleting "licenses" folder worked like a charm. I'm now living in the timewarp known as Media Composer 7. THANKS!
Welcome.... this is exactly what the forums are all about. Helping others!!!!
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller