"Can't find the Intel graphics" error

passionfly1 wrote on 1/3/2019, 4:31 AM

Starting Magix Audio Cleaning Lab 2017 (version 22.0.1.22) gives this error:

I have the latest version of Intel graphics installed (DCH 25.20.100.6471) on Windows 10 Pro (OS build 17763.195, 64-bit version)

My AMD software is up-to-the-minute latest version of 18.12.3 of Radeon installed and here is the latest OpenGL it comes with (version 25.20.15000.13543):

I have tried the latest version (I assume since its a year old) of QT_fixer_CL.exe (version 3.3.8.1) and it gives me this error:

The QT_fixer as I am aware is the latest available at this link:
https://support2.magix.com/customer/en/download_do/251629
If there a new one I am not aware of it because that link was posted in 2017 and that was over a year ago. Everyone seems to reference this link so I used it. It does not work.

I am getting extremely tired of the lack of PHONE SUPPORT for the hundreds of dollars of money spent on Magix software to only do forum support. I have problems with some sort of Magix software EVERY SINGLE WEEK. This is getting very very old and tiresome to fight my software as new problem occurs weekly. I just want to work and not deal with this >.<

Comments

ralftaro wrote on 2/12/2019, 7:59 AM

The QT_fixer as I am aware is the latest available at this link:
https://support2.magix.com/customer/en/download_do/251629
If there a new one I am not aware of it because that link was posted in 2017 and that was over a year ago. Everyone seems to reference this link so I used it. It does not work.

Sorry, but can you please be more specific as to how this fix isn't working? What (error) message does it report back when you run it on your system?

Other than that, I'd recommend taking this up with MAGIX support directly, if you haven't done so yet.

passionfly1 wrote on 2/15/2019, 6:26 AM

This is the specific error I am getting when I unpack the zip file and run the executable (which is also posted above). This fix does not work and no link to go to address this (other than the obvious Support portal link which creates a loopback to just downloading the same broken fix). =/

FYI, my date/time on my computer is set correctly so its not an issue with the EXE thinking its the wrong year or something.

Any ideas?

emmrecs wrote on 2/15/2019, 6:51 AM

@passionfly1

When did you actually download that file? I ask because I have just downloaded the current one, unzipped it and see a rather later modified date than is shown in your screenshot (see below):

Perhaps try downloading it again?

HTH

Jeff

ralftaro wrote on 3/6/2019, 3:23 AM

This is the specific error I am getting when I unpack the zip file and run the executable (which is also posted above). This fix does not work and no link to go to address this (other than the obvious Support portal link which creates a loopback to just downloading the same broken fix). =/

FYI, my date/time on my computer is set correctly so its not an issue with the EXE thinking its the wrong year or something.

Any ideas?

This is indeed a problem with an outdated version of the file having been cached somewhere. This could either be a local caching issue on your end (i.e. with your web browser), if you downloaded the outdated version of the file before, or it could be some caching mechanism in the content management system of the MAGIX support website itself. (Some users have made credible cases in the past that they received outdated versions of files hosted on the support website, despite never actually having downloaded that outdated version on their local system before, which is a bit confusing. Might be some Drupal CMS thing, but the support website is going to be replaced with a new solution anyway.) You should try deleing your local browser cache and then downloading from the given URL again.

https://support2.magix.com/customer/en/download_do/251629

From my experience, it also works if you explicitly force the web browser to save to a custom location on your hard drive, rather than just having it download and open the file from the default downloads/temp location. One way or another, I can assure you that a functional version fo the fix is hosted under the URL above, and has been since the beginning of January.