NEW! PaintShop Pro 2019

Faulting module MFC80.DLL, version 8.0.50727.1833

Faulting module MFC80.DLL, version 8.0.50727.1833

Postby lancea » Sun Oct 05, 2008 12:37 am

Yesterday I purchased 2 licences for WinDVD Plus Blu-ray, and installed it on my Vista Ultimate 32-bit (SP1) PC and Win XP Pro 32-bit (SP3) laptop. I've also installed a trial version of WinDVD Plus on a second XP laptop.

In all cases I'm getting the message "WinDVD MFC Application has stopped working" within a few seconds of the application window appearing. Windows Application event log shows this (example from my Vista PC) "Faulting application WinDVD.exe, version 9.0.14.91, time stamp 0x489aed03, faulting module MFC80.DLL, version 8.0.50727.1833, time stamp 0x482bc3e3, exception code 0xc0000005, fault offset 0x0004c0f3, process id 0x1f08, application start time 0x01c926662491f7d2".

I've gone through all recommendations I've found in this forum, namely uninstall + manual cleanup + reinstall with no firewall/antivirus; also installed the VB6 SP6 runtime components. It appears that none of these suggestions is addressing the issue.

My machines all have multiple copies of MFC80.dll, but only a couple of versions. In each case WinDVD.exe is loading version 8.0.50727.1833. The best explanation of why is here: http://phpbb.ulead.com.tw/EN/viewtopic.php?t=32691&highlight=mfc80+dll. A fairly good overview of WinSxS is here: https://thinstall.com/thintalk/viewtopic.php?p=360.

So, some questions - (1) Does anyone have WinDVD successfully running with MFC80.DLL version 8.0.50727.1833? (2) When I look at the manifest file in my WinDVD folder it refers to MFC80.DLL v8.0.50608.0. (3) Is this version necessary for WinDVD to run? If so, (4) how do I force it to use that version?

Thanks. I've spent hours trying to resolve this :-(
Last edited by lancea on Mon Oct 06, 2008 1:49 am, edited 1 time in total.
lancea
 
Posts: 16
Joined: Sat Oct 04, 2008 8:10 am

Postby migeror » Sun Oct 05, 2008 8:36 am

I have the same problem and want to know it too.
Nothing is better than spending money on the right thing, keep running for the economy growth -- 10km runner
migeror
 
Posts: 5
Joined: Fri Oct 03, 2008 7:13 am
Location: HK

Postby lancea » Wed Oct 08, 2008 6:16 am

migeror wrote:I have the same problem and want to know it too.

I submitted a support ticket for this issue and got a response a few hours ago. It was just a template reply so simply suggested the things I'd already done (several times on each installation). Fingers crossed that my report will be read and that the issue will be escalated.
lancea
 
Posts: 16
Joined: Sat Oct 04, 2008 8:10 am

Postby lancea » Fri Oct 10, 2008 9:53 pm

For anyone watching this - I am still working through this with Corel Support. No progress yet. I have tried everything suggested, on all 3 PCs that are giving the error. Fingers crossed.

If there's anyone a little bit technical who has WinDVD 9, I'd be very grateful if you could use Sysinternals Process Explorer (http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) to see what version of MFC80.DLL is being used by WinDVD.exe. Mostly, I want to know if it works with the version I have.
lancea
 
Posts: 16
Joined: Sat Oct 04, 2008 8:10 am

Postby lancea » Sat Oct 18, 2008 10:17 am

I have made progress on this. Corel Support advised that their WinDVD was running with MFC80.DLL verision 8.0.50727.762, and suggested I uninstall Visual Studio 2008 and - if that didn't do the trick - to reformat. Given that one of my laptops does not have VS2008, I didn't try uninstalling it. Reformatting isn't an option.

The issue, as identified by an earlier posting, is that XP and Vista keep multiple versions of common DLLs in a WinSxS (Side-by-Side) folder. Applications can ask for particular versions of DLL, and this is defined in the manifest file you see in the Corel\WinDVD folder. It is possible to edit a manifest file to make the application use DLLs from the application folder, in which case you'd just need to copy the appropriate versions of the common DLLs there. Alas, the manifest is also compiled into WinDVD.exe, and that's the copy that the application uses. WinDVD is asking for the latest version of mfc80.dll. If you have version 8.0.50727.1833 then WinDVD will crash.

WARNING - DON'T FOLLOW MY TEMPORARY WORKAROUND UNLESS YOU ARE TECHNICAL ENOUGH TO PUT THINGS BACK THE WAY THEY WERE

I managed to get WinDVD running on XP by doing the following:
1. Renamed "C:\Windows\winsxs\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.1833_x-ww_2fd6f5db\mfc80.dll" to mfc80.dll.sav
2. Copied "C:\Windows\winsxs\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05\mfc80.dll" to the above folder.

Clearly if you run an application that needs the correct dll in the "".1833" folder, anything could happen. There are tales on the web of people who have hosed their XP and Vista by deleting files from WinSxs, so the above was only done to prove that the error could be fixed by the developers. Vista has strong protection on the WinSxS folders and files, and the structure is somewhat different, so I'm not sure if this will work on Vista.
lancea
 
Posts: 16
Joined: Sat Oct 04, 2008 8:10 am

Postby sjj1805 » Sat Oct 18, 2008 12:33 pm

That is a great piece of information, I had never heard of the WinSxS (Side-by-Side) folder before.

I will copy a link to this possible cure in our FAQ.
sjj1805
 
Posts: 14914
Joined: Wed Jan 26, 2005 7:20 am
Location: Birmingham UK
operating_system: Windows XP Pro
System_Drive: C
32bit or 64bit: 32 Bit
motherboard: Equium P200-178
processor: Intel Pentium Dual-Core Processor T2080
ram: 2 GB
Video Card: Intel 945 Express
sound_card: Intel GMA 950
Hard_Drive_Capacity: 1160 GB

Postby lancea » Sun Oct 19, 2008 12:09 am

Thanks for the comment. I confess that I'd not heard of it either before I bought WinDVD. And it is a critical part of Windows, which is why it's so well protected on Vista. So, I'm learning, and now have what I think is a better temporary workaround for XP.

On Windows XP only:
1. Using Windows Explorer, go to folder C:\Windows\WinSxS\Policies\x86_policy.8.0.Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_x-ww_0f75c32e
Then EITHER
2 (a) Rename file "8.0.50727.1833.policy" to "8.0.50727.1833.policy.save"
OR
2 (b) Edit file "8.0.50727.1833.policy" as follows
(i) Save a copy of the file, then open the original in a text editor
(ii) Change this line:
<bindingRedirect oldVersion="8.0.41204.256-8.0.50608.0" newVersion="8.0.50727.1833"/>
To this:
<bindingRedirect oldVersion="8.0.41204.256-8.0.50608.0" newVersion="8.0.50727.762"/>
(c) Save the file
3. Now run WinDVD, and it will hopefully work.

The second alternative is I think more correct since applications requesting later versions of the MFC DLLs should get the correct ones.

As for Vista - this is really hard. The equivalent file is "C:\Windows\winsxs\Manifests\x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.1833_none_49ed4131141912ee.manifest". However, on Vista the owner of the WinSxs folders and files is TrustedInstaller, which has higher powers than SYSTEM and Administrators. The ONLY thing that's meant to make changes here is Windows Installer packages. You can change the owner of a file BUT - I did so and can no longer get the above policy-file back into the folder. :(

Corel has issued a hotfix for an X4 product that addresses an issue with the version "1833" DLLs, so I'm hoping I can finally persuade WinDVD Support to pass this on to the developers and that they will issue a fix for WinDVD. This issue will hit more and more people as time goes on.
lancea
 
Posts: 16
Joined: Sat Oct 04, 2008 8:10 am

Postby Ron P. » Sun Oct 19, 2008 12:20 am

I'll just add a quick comment concerning tampering with Vista's Trusted Installer permissions. DON'T DO IT. I did it, trying to get a DLL file pasted into a folder that the Trusted Installer was the only one having permission to do so. I hosed my system, and had to reformat and reinstall my OS..
Ron Petersen, Web Board Administrator
User avatar
Ron P.
Site Admin
 
Posts: 12197
Joined: Tue May 10, 2005 12:45 am
Location: Kansas, USA
operating_system: Windows 10
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: Hewlett-Packard 2AF3 1.0
processor: 3.40 gigahertz Intel Core i7-4770
ram: 16GB
Video Card: NVIDIA GeForce GTX 645
sound_card: NVIDIA High Definition Audio
Hard_Drive_Capacity: 4TB
Monitor/Display Make & Model: 1-HP 27" IPS, 1-Sanyo 21" TV/Monitor
Corel programs: VS5,8.9,10-X5,PSP9-X8,CDGS-9,X4,Painter

Postby sjj1805 » Sun Oct 19, 2008 12:40 am

lancea wrote:.......
WARNING - DON'T FOLLOW MY TEMPORARY WORKAROUND UNLESS YOU ARE TECHNICAL ENOUGH TO PUT THINGS BACK THE WAY THEY WERE
......


Just to emphasise the advice previously given by the author of this procedure. Always make sure that YOU are able to undo anything that you alter.
sjj1805
 
Posts: 14914
Joined: Wed Jan 26, 2005 7:20 am
Location: Birmingham UK
operating_system: Windows XP Pro
System_Drive: C
32bit or 64bit: 32 Bit
motherboard: Equium P200-178
processor: Intel Pentium Dual-Core Processor T2080
ram: 2 GB
Video Card: Intel 945 Express
sound_card: Intel GMA 950
Hard_Drive_Capacity: 1160 GB

Postby lancea » Fri Oct 24, 2008 9:07 am

Corel Support have just advised me that this issue has now been forwarded to the developers, so hopefully an update will appear reasonably soon.

After working around the problem on XP by editing the WinSxS policy file for the MFC assembly, I was able to do the same thing on Vista. The only reason I mention that is to assure anyone who cannot run WinDVD on Vista that it is the same issue. You cannot simply edit the file as you do on XP, and I think it would do more harm than good to post how it can be done. The only safe solution is to wait for a patch from Corel.
lancea
 
Posts: 16
Joined: Sat Oct 04, 2008 8:10 am

Postby Ron P. » Fri Oct 24, 2008 10:21 am

Thanks for posting that information..:)

FWIW, my problem with Vista was not trying to correct this issue. It was with another totally different one, I had/have with VS 12 and rendering FLV. But none the less any folder, file that the Trusted Installer is the only one granted permission, do not mess with it. It makes Vista very, very, angry.
Ron Petersen, Web Board Administrator
User avatar
Ron P.
Site Admin
 
Posts: 12197
Joined: Tue May 10, 2005 12:45 am
Location: Kansas, USA
operating_system: Windows 10
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: Hewlett-Packard 2AF3 1.0
processor: 3.40 gigahertz Intel Core i7-4770
ram: 16GB
Video Card: NVIDIA GeForce GTX 645
sound_card: NVIDIA High Definition Audio
Hard_Drive_Capacity: 4TB
Monitor/Display Make & Model: 1-HP 27" IPS, 1-Sanyo 21" TV/Monitor
Corel programs: VS5,8.9,10-X5,PSP9-X8,CDGS-9,X4,Painter

Postby sjj1805 » Fri Oct 24, 2008 11:10 am

Upon reading this cure I immediately thought of several other niggling issues which have affected various Ulead/Corel items of software.
Let us hope that the engineers use this newly found issue to resolve some of those at the same time.

One such example is failing to importing from a DVD, some items of Corel software conflicts with others.
sjj1805
 
Posts: 14914
Joined: Wed Jan 26, 2005 7:20 am
Location: Birmingham UK
operating_system: Windows XP Pro
System_Drive: C
32bit or 64bit: 32 Bit
motherboard: Equium P200-178
processor: Intel Pentium Dual-Core Processor T2080
ram: 2 GB
Video Card: Intel 945 Express
sound_card: Intel GMA 950
Hard_Drive_Capacity: 1160 GB

Postby lancea » Fri Oct 24, 2008 10:46 pm

Changes to the OS and development tools (like Xcopy installs and WinSxS) were supposed to resolve most of the mixed-DLL problems. In the late 80s and through the 90s when I was doing development, they were the most difficult issues to resolve. We've come a long way ;-) But really it is pretty neat how Vista and XP can both self-repair to a fair extent. If the WinSxs folders weren't so well protected I guess they wouldn't be very helpful at all. I think developers can package their custom application DLLs and install them in WinSxS, but I don't see that in my folders. So the kind of fix you've had to do will be needed till all application behave well. In this case I'm not even sure if the WinDVD developers have done anything inappropriate. The WinSxS policy for MFC80 says that the DLL assembly that WinDVD needs is compatible with the very latest version. At least I think that's what it says.

The twist in my finding a temporary workaround is that DVDs are jerky on my PC, even when I copy the DVD to a hard disk. CPU is below 50% and the video card should be easily up to the task. I've got 2GB RAM with plenty free. So I guess my single-core 2.8GHz CPU and the hardware bus just don't cut the mustard. Our dollar is plumeting- $NZ1.00 buys $US0.55 today, whereas a year ago it bought $US0.78, so perhaps it's time to look at building a new PC. Sigh. I recall this happening last time I upgraded Flight Simulator :roll:
lancea
 
Posts: 16
Joined: Sat Oct 04, 2008 8:10 am

Postby mogulman » Tue Dec 09, 2008 4:27 pm

Any news on this? I have this error when I shut down Windvd9 and also intermittently when playing.
mogulman
 
Posts: 8
Joined: Tue Dec 09, 2008 1:23 am

Postby lancea » Tue Dec 09, 2008 8:52 pm

Hi mogulman. Which error are you getting? The MFC error will stop you running WinDVD, and there appears to be no official fix for that (there's nothing on the updates page). If you mean jerkiness, then I resolved that by building a new PC with a Core 2 Quad processor. I doubt there's any other answer - except lowering graphics resolution, getting a faster video card, more memory and perhaps updating your DVD player. Makes for an expensive DVD player!
lancea
 
Posts: 16
Joined: Sat Oct 04, 2008 8:10 am

Next

Return to WinDVD

Who is online

Users browsing this forum: No registered users and 1 guest