Windows 10 Anniversary ed'n broke my Media Manager


NickHope wrote on 8/29/2017, 9:47 AM

Someone on the Acid forum said they got MM working in Acid Pro 7 by starting it with administrator rights. Quite possibly a different issue, but it might be worth trying with Vegas before resorting to virtual machines etc.:

By the way, from Vegas Pro 15, "Enable Media Manager" is now an internal preference (reached by holding SHIFT while clicking Options > Preferences)

NickHope wrote on 9/20/2017, 7:12 AM

A heads up for anyone who thought they'd frozen Windows 10 at version 1511 for MM compatibility by turning off the Windows Update service:


Edit: See clarifications from MAGIX on Media Manager's future in this post.

NickHope wrote on 10/25/2018, 4:19 AM

For the forgotten millions still running outdated Windows so they can run Media Manager (What? Only me??) I have been able to get Media Manager running in VirtualBox using these versions:

  • Host OS: Windows 10 Pro version 1511
  • VirtualBox 5.2.20 r125813 (Qt5.6.2)
  • Guest OS: Windows 10 Pro version 1511
  • VEGAS Pro 14 build 270
  • Media Manager 2.4b


I gave VirtualBox 4096MB base memory and the default 50GB virtual HDD.

I was able to open my video.medialib of 21k assets and my audio.medialib of 4k assets in Media Manager. It is a bit slow and clunky compared to running natively. 4k previews badly. But so far it's functional and provides a way to access the database in the future, from more up-to-date versions of Windows.

Surprisingly I didn't need to install any SQL stuff manually. I made sure the internet connection was working in VirtualBox and then the MM installer went off and very quickly fetched the 2 dependencies that it needed.

You will need a spare VEGAS Pro license to do this, as VEGAS doesn't know that it's on the same hardware, since it's running in a virtual machine. The Magix Vegas Pro license is good for 2 computers. Or use a license for an old version just for this.

I am doing this test with a "special" edition of Windows 10 version 1511 (don't ask) but apparently Windows 10 does not need to be activated anyway; it will run with a watermark. You can't easily get a Win10 1511 ISO officially, but "hedmon" in this thread posted a link to an ISO that is still live (I'm currently downloading it). And there is this possibility too, but it's a larger file that includes the x86 version. I can't vouch for the safety of either. Or you can install from an older Win 10 version and update until this update then stop. Or Win7, 8.1 etc..

If you do this, turn off Windows updates in the guest Windows as soon as you can in the Group Policy Editor.

Personally, I will probably soldier on with my Windows 10 version held at 1511 and then try this route when I next upgrade my computer.

john_dennis wrote on 10/25/2018, 12:59 PM

"I am doing this test with a "special" edition of Windows 10 version 1511 (don't ask)..."

In the past, I've used the VMWare Physical to Virtual (P2V) converter to create virtual machines from old hardware/OS/software machines. Using this method, you could freeze a virtual machine of an earlier maintenance level of your Windows 10 system or an image of that old decrepit Windows 8.1 hardware box that's on it's last legs. Does Virtual Box have a similar tool?

This is all mind-fodder to me since the only virtual machines that I keep personally are my TurboTax system and a Windows 2000 system that has an antiquated version of AutoCAD. I just realized I'm getting less and less curious about these things since they stopped paying me to do it.

My main system:
Motherboard: ASUS ProArt Z790-CREATOR WIFI
CPU: Intel Core i9-13900K - Core i9 13th Gen Raptor Lake 24-Core (8P+16E) P-core Base Frequency: 3.0 GHz E-core Base Frequency: 2.2 GHz LGA 1700 125W Intel UHD Graphics 770 Desktop Processor - BX8071513900K
GPU: Currently intel on-die video adapter
RAM: CORSAIR Vengeance 64GB (2 x 32GB) 288-Pin PC RAM DDR5 5600 (PC5 44800) Desktop Memory Model CMK64GX5M2B5600C40
Disk O/S & Programs: WD Black SN850 NVMe SSD WDS100T1X0E - SSD - 1 TB - PCIe 4.0 x4 (NVMe)
Disk Active Projects: 1TB & 2TB WD BLACK SN750 NVMe Internal PCI Express 3.0 x4 Solid State Drives
Disk Other: WD Ultrastar/Hitachi Hard Drives: WDBBUR0080BNC-WRSN, HGST HUH728080ALE600, 724040ALE640, HDS3020BLA642
Case: LIAN LI PC-90 Black Aluminum ATX Full Tower Case
CPU cooling: CORSAIR - iCUE H115i RGB PRO XT 280mm Radiator CPU Liquid Cooling System
Power supply: SeaSonic SS-750KM3 750W 80 PLUS GOLD Certified Full Modular Active PFC Power Supply
Drive Bay: Kingwin KF-256-BK 2.5" and 3.5" Trayless Hot Swap Rack with USB 3
Sound card: Realtek S1220A on motherboard. Recording done on another system.
Primary Monitor: ASUS ProArt 31.5" 1440p HDR10 Monitor PA328QV
O/S: Windows 10 Pro 10.0.19045 Build 19045
Camera: Sony RX10 Model IV

NickHope wrote on 10/25/2018, 1:58 PM

That's a very useful heads-up John. A Google for "virtualbox physical to virtual converter" turns up a few leads including disk2vhd from Sysinternals.

However there's so much old hidden rubbish on this box after 4 years. My C: has 134GB on it even after a recent good cleanup, and that's without docs/downloads/pictures/videos. The worst space-wasting culprit I found was Filmconvert. Multiple versions remaining, despite "updating". Multiple huge installers left behind in obscure places.


I used to use it in another life and when I needed to do some house plans 5 years ago I found that Draftsight was a good free alternative. Everything worked pretty much the same as AutoCAD. Can't help you with the tax.

EDIT: There was some discussion about Media Manager following my comment here, which leads into JN_'s comment below.

Former user wrote on 10/5/2019, 10:22 AM

@NickHope Indeed, it was only after I had Posted in the previous thread that I realised that something like Access might not handle the media type.

I was then going to suggest using an old legacy machine, until something came along, but looking at your above post I guess that thats where your at anyway.

zdogg wrote on 10/5/2019, 2:42 PM

@NickHope Nick, I downloaded Media Manager, (thanks) mostly out of curiosity, and got it to load up in VP 17 and I must say, it's working quite well so far, and I love the way it puts the clip right into the Trimmer. I am running the dinosaur Win 7 64..... so, I'm sure that is the difference maker. What advantages would one experience on Win 10...I don't appreciate it's intrusiveness, don't like it locking you out of previously more easily configurable features (sure, there are workarounds, who has the time to figure all of tht out?) and so I've tried it out, found it wanting, and went back to 7.

What I would say is that it is better suited to the machine I'm using now, as opposed to way back when MM first came out, faster, more RAM, SSDs, better video cards, and so forth. It's also not crashing Vegas, at least not yet, knock on wood.

IF one would not be able to use MM in Win 10, I would suggest that Adobe Bridge is pretty robust in that arena, though I'm just getting on to that one as well. I think one can individually rent Adobe programs, if not interested in Adobe Cloud suite.

BTW, and tips and tricks instructional videos you'd recommend for Media Manager?

NickHope wrote on 10/6/2019, 6:06 AM

@NickHopeBTW, and tips and tricks instructional videos you'd recommend for Media Manager?

@zdogg Actually I don't remember ever watching any videos about Media Manager. I think I just worked it out as I went along, with a little assistance from this forum.

I would not recommend putting any serious time or effort into Media Manager now. At some point you'll very likely have to move to Windows 10 as applications simply won't work on Windows 7 any more.

I see that Vee-Hive is still going and still free/cheap. Might be a better tool for you to try.

NickHope wrote on 10/7/2019, 2:23 AM

One workaround not mentioned previously is the possibility to access Media Manager on an old networked machine via Remote Desktop. Unfortunately it appears drag and drop is not supported on Remote Desktop, so files would have to be added to a VEGAS project on the remote machine, then that project opened on the new machine.

It would be a hassle to have to run 2 machines, and set up networked or duplicate storage, but it's a possibility if a virtual machine just isn't up to the job.