Setup BD-RB with Win 7

[Capsbackup]

My curiosity has done me in!
I wanted to see if I could run Windows 7 on my I7 920 computer, and after running the Win 7 update advisor, it warned me there could be some conflicts. The challenge was on.
I decided to try the Ultimate edition RC, since it was free, and if I did not like it or it did not seem worth the upgrade price, it would expire soon enough and only a few hours would be waisted. ( waisted plenty in my time! ):)
Well, all installed fine, and after searching around for updated drivers for some hardware, all was a go.
Now trying BD-RB, all is not so well.:o
I can't seem to get it to even start up, I get this error:
"Component MSCOMCTL.OCX or one of it's dependencies not correctly registered: a file is missing or invalid"
I try the fix - "Look in the BD-RB folder. There is a .BAT file called "REG_MSCOMCTL.BAT" -- simply right click onit and run it as administrator."
But then I get this - The Module MSCOMCTL.OCX failed to load... So this does not work for me.
Can BD-RB run with Windows 7 RC?
How else can you get rid of this MSCOMCTL.OCX REG issue just to get BD-RB to start?
After reading back numerous pages, I can't seem to find out what to do next. Any help is sure appreciated.:confused:

EDIT:
OK, I got it to work by right clicking on BD_Rebuilder and selecting "Run as Administrator", which it then set up ffdshow for me, and now it starts up.
Off to try out a backup! :p

[datman]

My curiosity has done me in!
I wanted to see if I could run Windows 7 on my I7 920 computer, and after running the Win 7 update advisor, it warned me there could be some conflicts. The challenge was on.
I decided to try the Ultimate edition RC, since it was free, and if I did not like it or it did not seem worth the upgrade price, it would expire soon enough and only a few hours would be waisted. ( waisted plenty in my time! ):)
Well, all installed fine, and after searching around for updated drivers for some hardware, all was a go.
Now trying BD-RB, all is not so well.:o
I can't seem to get it to even start up, I get this error:
"Component MSCOMCTL.OCX or one of it's dependencies not correctly registered: a file is missing or invalid"
I try the fix - "Look in the BD-RB folder. There is a .BAT file called "REG_MSCOMCTL.BAT" -- simply right click onit and run it as administrator."
But then I get this - The Module MSCOMCTL.OCX failed to load... So this does not work for me.
Can BD-RB run with Windows 7 RC?
How else can you get rid of this MSCOMCTL.OCX REG issue just to get BD-RB to start?
After reading back numerous pages, I can't seem to find out what to do next. Any help is sure appreciated.:confused:

I had the same problem about a year ago I received alot of help here is the page where I was told how to fix it. Just read down I'm sure you will figure it out better that I did.

http://85.230.118.136/showthread.php?p=1253359#post1253359

[jdobbs]

My curiosity has done me in!
I wanted to see if I could run Windows 7 on my I7 920 computer, and after running the Win 7 update advisor, it warned me there could be some conflicts. The challenge was on.
I decided to try the Ultimate edition RC, since it was free, and if I did not like it or it did not seem worth the upgrade price, it would expire soon enough and only a few hours would be waisted. ( waisted plenty in my time! ):)
Well, all installed fine, and after searching around for updated drivers for some hardware, all was a go.
Now trying BD-RB, all is not so well.:o
I can't seem to get it to even start up, I get this error:
"Component MSCOMCTL.OCX or one of it's dependencies not correctly registered: a file is missing or invalid"
I try the fix - "Look in the BD-RB folder. There is a .BAT file called "REG_MSCOMCTL.BAT" -- simply right click onit and run it as administrator."
But then I get this - The Module MSCOMCTL.OCX failed to load... So this does not work for me.
Can BD-RB run with Windows 7 RC?
How else can you get rid of this MSCOMCTL.OCX REG issue just to get BD-RB to start?
After reading back numerous pages, I can't seem to find out what to do next. Any help is sure appreciated.:confused:

EDIT:
OK, I got it to work by right clicking on BD_Rebuilder and selecting "Run as Administrator", which it then set up ffdshow for me, and now it starts up.
Off to try out a backup! :pLook in the BD-Rebuilder folder. Right click on the file called "REG_MSCOMCTL.BAT" and select "Run as Administrator". It will register the .OCX file.

[Capsbackup]

I tried that, but it would not work. Kept giving me this error:

The Module MSCOMCTL.OCX failed to load...
What did finally work was clicking on BD_Rebuilder.exe and selecting "Run as Administrator", which it then set up ffdshow for me, and now it starts up.

[jdobbs]

I tried that, but it would not work. Kept giving me this error:

What did finally work was clicking on BD_Rebuilder.exe and selecting "Run as Administrator", which it then set up ffdshow for me, and now it starts up. That's weird.

[Capsbackup]

That's weird.

I thought so too. I had been following the trials and tribulations, the Windows 7 saga :p, waiting to see if the bugs were worked out before I was to give it a try.
So, just when I decide it was all quiet on the Win 7 bug report, and I jump in, then this pops up.:rolleyes:
Oh well, it is working now!
I have one movie only backup complete, and it turned out just fine.:)
I will give this RC more testing before I decide to make the move, but so far it looks good!:D

[massiah]

Yeah, I just upgraded my Vista Ultimate to Win 7 Ultimate.

I am getting my office floor re-tiled and was sitting around when I realized that BD Rebuilder has not been tesed with Win 7 according to the home page.
Thanks for this info and I will try and test it out when I get my office back in order.

[jdobbs]

Yeah, I just upgraded my Vista Ultimate to Win 7 Ultimate.

I am getting my office floor re-tiled and was sitting around when I realized that BD Rebuilder has not been tesed with Win 7 according to the home page.
Thanks for this info and I will try and test it out when I get my office back in order. Hmmm... that was old information and isn't true anymore. I forgot about posting it and have just removed that statement. BD-RB has been tested, and I am currently running it on both the 64 bit and 32 bit versions of Windows 7.

The big secret to avoiding problems with Windows 7 is to let BD-RB configure DirectShow for you when it runs the first time -- and don't change the settings afterward.

[ChBrig]

Hmmm... that was old information and isn't true anymore. I forgot about posting it and have just removed that statement. BD-RB has been tested, and I am currently running it on both the 64 bit and 32 bit versions of Windows 7.

The big secret to avoiding problems with Windows 7 is to let BD-RB configure DirectShow for you when it runs the first time -- and don't change the settings afterward.

Hi,

I would like also to upgrade my vista family premium 64bit to Windows 7 family premium 64bits. BD Rebuilder is working perfectly with my Vista.
What do you mean by "to let BD-RB configure DirectShow for you when it runs the first time -- and don't change the settings afterward.[/QUOTE]"?
What does I do exactely?

[ChBrig]

Hi,

I would like also to upgrade my vista family premium 64bit to Windows 7 family premium 64bits. BD Rebuilder is working perfectly with my Vista.
What do you mean by "to let BD-RB configure DirectShow for you when it runs the first time -- and don't change the settings afterward."?
What does I do exactely?[/QUOTE]

Sorry: what must I do exactely?

[Ch3vr0n]

you don't have to do anything. BD-RB will make the required changes for you and this will only take a few seconds. Afterwards your good to go and start rebuilding.

[Adub]

I have had a number of users coming to me for help with BD-Rebuilder on Windows 7 on my website.

Would it be possible to add a feature that will check if a VC-1 DirectShow chain will work before any encoding is done? Something like "Check VC-1 Settings", which could return any errors (including Avisynth generated ones) in a comprehensive report?

It would make diagnosing Windows 7 problems a lot easier, as I currently do not have a Windows 7 install and I repeatedly hear about issues that seem to fix themselves (or break themselves).

[Capsbackup]

@Adub;
I believe if someone has Windows 7, and they want to use BD-Rebuilder, and they have haali, ffdshow and avisynth installed, the first time they try to start the program it will setup ffdshow for all containers. ( it did for me anyway )

[jdobbs]

@Adub;
I believe if someone has Windows 7, and they want to use BD-Rebuilder, and they have haali, ffdshow and avisynth installed, the first time they try to start the program it will setup ffdshow for all containers. ( it did for me anyway ) In fact, if they don't have FFDSHOW installed, it will tell them so. Then, when you run it again (after installing) it will set all the codecs properly. The problems almost all are related to people who decide they know too much and install "updated" versions of the support packages and get trapped in new bugs... I also run into a lot of people who decide to put their own version of X264 to use -- which causes encode failures because it doesn't support --nal-hrd (which is provided through a patch).

[Jake802]

I just did a fresh install of windows 7 ultimate 64-bit and now I cant get BD to work? I keep getting the configuration msg followed by a runtime error. Any ideas?

[Capsbackup]

Make sure you only install Haali, FFDSHOW and Avisynth 2.57, found at the first page of the BD-RB bugs report thread.( same place you download BD-RB)
If you installed any other versions, uninstall them, reboot, and install the preferred ones. If you installed any other codec packs, uninstall them too.
Then unzip a fresh new BD-RB, right click on "REG_MSCOMCTL.BAT" and select run it as administrator."
Then, if that does not work, right click on BD_Rebuilder.EXE and select "Run as Administrator" .

[Jake802]

Thanks!

That appeared to work now to test it out!

Thanks Again!

Jake

[Adub]

Okay, it's as I thought. I will refer everyone to this thread.

[bokker]

Hello i let BD rebuilder with instalate as Administrator and the when i say 2 times yes oke and i staart inspection this is i see?

http://i53.tinypic.com/2d282za.jpg

WIN& Preferred MPEG2 CODEC: not set correctly?

I let BD rebuileder do the settings and i make sure i do it ass Administrator but evryrtime i start Br rebuilder i most set settings .

Some one solution ?:thanks:

i have windows 7 64bit

[Capsbackup]

My Win 7 32 bit ffdshow video decoder settings has MPEG2 as Libmpeg2, and Other MPEG2 as disabled.
You could try to uninstall haali, ffdshow and Avisynth, delete the folder for haali in ALL Programs, reboot and then reinstall those three programs.
Then delete the BDREBUILDER configuration settings file inside the unzipped BD-RB folder. First right click on REG_MSCOMCTL and Run as Administrator. Then right click on BD_Rebuilder.exe and run as Administrator.
This has always worked for me, but you need to do each and every step, no skipping uninstalls and reinstalls! :cool:

[bokker]

i dit everyting you say Capsbackup but its the same

http://i53.tinypic.com/2d282za.jpg

WIN7 Preferred MPEG2 CODEC: not set correctly?

Are there a codec missing? I.dont now.
And everethime i start bd rebuilder i get the message windows not configred with ffdshow.
So i let BD rebuilder do it for me and answer with yes.
Get then message windows 7 system has been successfully configured to use ffshow with rebuilder , can uyou explain why above the message : WIN7 Preferred MPEG2 CODEC: not set correctly?
When i run Inspect?
it is not necessary that well to put?

Are it not

regards bokker

[jdobbs]

It means that even though you have FFDSHOW installed, it is not the preferred codec and some other one might be used.

Since the others are set correctly, some other program had to have changed it. Probably something you've installed recently.

Right click on the file FF_RESET.BAT in your BD-RB folder and say "Run as Administrator". This will set the values back to their original state. Then right click on BD_Rebuilder.exe and say "Run as Administrator". It will then see that they need to be set and will do it correctly again. Make sure you say "Yes" when it asks you if it's ok to change them.

[bokker]

This are my BD Rebuilder folder i can find there FF_RESET.BAT
For make sure i have this verson of BD Redbuilder BD-RBV03701

http://i51.tinypic.com/1zfh0km.jpg

And this are setting for FFShow

http://img718.imageshack.us/img718/6263/screenshot014r.png

[jdobbs]

If it doesn't exist -- that means they were never set in the first place by BD-RB (because it saves the original values to that file before changing them).

The FFDSHOW settings aren't the issue. It's the Windows 7 preference settings. If they point elsewhere, FFDSHOW is simply ignored.

If you don't mind editing your registry yourself, you can put the line below into a .BAT file and run it as administrator. Remember, though, that editing the registry can sometimes be risky, and you are doing so at your own risk:

reg add HKLM\SOFTWARE\Microsoft\DirectShow\Preferred /v {e06d8026-db46-11cf-b4d1-00805f6cbbea} /t REG_SZ /d {04FE9017-F873-410E-871E-AB91661A4EF7} /f

[bokker]

If it doesn't exist -- that means they were never set in the first place by BD-RB (because it saves the original values to that file before changing them).

The FFDSHOW settings aren't the issue. It's the Windows 7 preference settings. If they point elsewhere, FFDSHOW is simply ignored.

If you don't mind editing your registry yourself, you can put the line below into a .BAT file and run it as administrator. Remember, though, that editing the registry can sometimes be risky, and you are doing so at your own risk:

reg add HKLM\SOFTWARE\Microsoft\DirectShow\Preferred /v {e06d8026-db46-11cf-b4d1-00805f6cbbea} /t REG_SZ /d {04FE9017-F873-410E-871E-AB91661A4EF7} /f


to the lower part of the drawing black line the number starts the same such as those I of you have. But those already in to register stood>
This key already there {e06d8026-db46-11cf-b4d1-00805f6cbbea} / {212690FB-83E5-4526-8FD7-74478B7939CD} i let it be

I dit the same you say here i make it in the register HKLM\SOFTWARE\Microsoft\DirectShow\Preferred /v {e06d8026-db46-11cf-b4d1-00805f6cbbea} /t REG_SZ /d {04FE9017-F873-410E-871E-AB91661A4EF7}

http://img225.imageshack.us/img225/9394/screenshot017i.png
And than i restar my computer and install all the progammas, I do Haali, FFDSHOW and Avisynth 2.57 i nothing chance this progams just install.
And at last right click on BD_Rebuilder.EXE and select "Run as Administrator" .
And when i take inspector i see again WIN7 Preferred MPEG2 CODEC: not set correctly?
When y als o run "REG_MSCOMCTL.BAT" and select run it as administrator." nothing happend al the same message,, WIN7 Preferred MPEG2 CODEC: not set correctly?

Only thing i see when i run BD rebuilder are a file BDREBUILDER configuratie.[Options]
VERSION=0.37.0.1
MODE=0
ENCODE_QUALITY=0
ONEPASS_ENCODING=2
AUTO_QUALITY=1
I let that so it is.


Sorry but i try


What do i do wrong?

[jdobbs]

Perhaps you don't have administrator privileges? Try logging in as admin and try again.

If you know how to use the registry editor, just manually change the value for {e06d8026-db46-11cf-b4d1-00805f6cbbea}" to "{04FE9017-F873-410E-871E-AB91661A4EF7}" under HKLM\SOFTWARE\Microsoft\DirectShow\Preferred.

[bokker]

Perhaps you don't have administrator privileges? Try logging in as admin and try again.

If you know how to use the registry editor, just manually change the value for {e06d8026-db46-11cf-b4d1-00805f6cbbea}" to "{04FE9017-F873-410E-871E-AB91661A4EF7}" under HKLM\SOFTWARE\Microsoft\DirectShow\Preferred.


Ther are two Value name one the one i make:
reg add HKLM\SOFTWARE\Microsoft\DirectShow\Preferred /v {e06d8026-db46-11cf-b4d1-00805f6cbbea} /t REG_SZ /d {04FE9017-F873-410E-871E-AB91661A4EF7} /f

And one whois already there.
{e06d8026-db46-11cf-b4d1-00805f6cbbea} {212690FB-83E5-4526-8FD7-74478B7939CD}

And must i change after REG_SZ ? sorry

[jdobbs]

If it was already there the command line would have changed the existing one.

There can only be one. If you look closely you'll see that the others are slightly different:

{e06d8026-db46-11cf-b4d1-00805f6cbbea} - This is the one you change
{e06d802b-db46-11cf-b4d1-00805f6cbbea}
{e06d8032-db46-11cf-b4d1-00805f6cbbea}

You double click on the value and paste in the new one and say "Okay".

Remember, though, you are editing your registry at your own risk... you have to be very careful not to change the wrong things.

[bokker]

i change this value {e06d8026-db46-11cf-b4d1-00805f6cbbea} {212690FB-83E5-4526-8FD7-74478B7939CD}

in to this value
{e06d8026-db46-11cf-b4d1-00805f6cbbea} {04FE9017-F873-410E-871E-AB91661A4EF7}

I install al again but stil i can see FF_RESET.BAT

and stil the message to see with inspector WIN7 preferred MPEG2 CODEC: Not Set correctly

Shut i give up jdobbs:confused: ???

I thank you verry mutch till now :thanks:

[jdobbs]

You will never see FF_RESET now. That only get's created when BD-RB sets all those values the first time it is run. You're doing it by hand.

Now that you've changed it, run INSPECT.EXE and you should see "Ok" for preferred MPEG-2 codec.

[bokker]

:thanks::thanks::thanks:yes this did the Job I thanks you verry verry mutch and you effort to help me thanks you:thanks:

Regards a happy bokker:):):)

[sbtuttle]

Hi,

I'm sure this question has been addressed many,many times. And if I was not having to be the sole caretaker of my 2yr grandson 24/7, I'd have the time to read all the threads and posts.

But I'm lucky just to have a few minutes alone.

If anyone can help with this one issue, I would owe big-time: running win 7 ultimate 32 bit, all bd software up to date

Only getting one error when I run "inspect", as follows

" WIN7 preferred VC-1 CODEC: Not Set correctly"

Where, and how do I set correctly?

Driving me nuts,

As I said, time is not on my side to research

Thanks in advance

Steve

[jdobbs]

1. Click on the Windows START button.
2. Click on "All Programs"
3. Scroll down to FFDSHOW and click
4. Select "Video Decoder Configuration"
5. Under "Codecs" (on the left), find VC-1 and select "wmv9"
6. Click on OK.

[sbtuttle]

Thanks for the reply,

The problem is that that is what it is set for, and I still get the error message.

When I start the program I also get a message, that I hope I attached correctly

Thanks,

Steve

[Capsbackup]

Uninstall ffdshow, reboot. Delete BDREBUILDER configuration settings file in BD-RB folder.
Reinstall ffdshow, the one recommended from 1st page of this thread.
Then:
There is a .BAT file called "REG_MSCOMCTL.BAT" -- simply right click on it and select "Run as Administrator".
Then right click on BD_Rebuilder.exe and select Run as Administrator.

[sbtuttle]

Followed directions of last post, now I get the following messages

As attachments, don't know how to insert into post

Wrong order,

Inspect

dshow

After I click "yes", I then get this message,

bd rebuild

all gif

[Capsbackup]

Uninstall any codec packs you installed. Any recent programs you installed? that may have installed video playback codecs?
Uninstall haali, avisynth and ffdshow. Delete the program folder for haali. Reboot.
Reinstall those three programs from page one and try again, following the instructions from page one. :cool:

[sbtuttle]

uninstalled all of the supporting programs, uninstalled re-builder,

rebooted

reinstalled in order listed, and only set the defaults, with exception to those mentioned in install post.

have not installed codec packs or playback software

It has to be a simple setting in ffdshow - just don't know which one

messages I know get will be attached

Thanks to all, I am very grateful for all the help

Steve

[jdobbs]

Some other program has to be changing that setting. When BD-RB tells you everything has been set correctly it is reading the exact same registry entry as INSPECT.

Make sure you right click and run as administrator the first time you run BD Rebuilder -- but I don't think that's it, since everything else seems to be set correctly.

[sbtuttle]

Hi,

Ran both the config and bd-rebuilder everytime as admin

Following is a list of all video related programs (can't remember if Auto GK is listed, but it's loaded, also have Anyhd, but it's not on if I use DVDfab

[Capsbackup]

Just my opinion, but your problem lies with one of those many listed programs you have installed. :(

[sbtuttle]

I'm using 7 Ultimate, I've got an unused copy of Vista Ultimate. If I install vista on a separate hdd and dual-boot.

Then install only the programs for bd-rebuilder, and it on Vista, follow the install as admin and rest of instructions - it should run correctly - Right?

Or would there be a problem from windows media center?

Thanks in advance

Steve

[MilesAhead]

I'm using 7 Ultimate, I've got an unused copy of Vista Ultimate. If I install vista on a separate hdd and dual-boot.

Then install only the programs for bd-rebuilder, and it on Vista, follow the install as admin and rest of instructions - it should run correctly - Right?

Or would there be a problem from windows media center?

Thanks in advance

Steve

Have you been able to get BDRB set up and complete one successful run? If so, usually what happens as jdobbs said, you run another program later and it changes settings.

If you have never been able to set up BDRB and complete a successful run, then you have another problem.

First diagnostic technique is narrow the location. Otherwise you'll be like the guy who lost his car keys at night. He's looking under the lamp post. Someone asks what he's looking for. He says "My car keys." The bystander asks "where did you drop them?" The car key searcher points across the street and says "over there." The bystander asks "then why are you looking on this side of the street?" The car key searcher says "because the light is better over here."

[sbtuttle]

No, I've never been ableto get the program to run, despite all the help, I stillhave an inspection error on VC-1, and when I run it it allways gives me the messege posted.

I have however, installed and run all programs as the instructions state on a old toshiba A65 laptop running win xp home

And after I change the mpeg2 setting in ffshow and run inspect EVERYTHING is correct.

So, Screw win 7, I'm waiting on the full xp home from ebay, and load it on my other Raptor drive and dual boot

I thank everyone with all my heart for all the help, but with having to watch my Grandson - I just don't have time to troubleshoot.

Thanks,

Steve

[Rich86]

I am running BD-RB under a Win7 Pro/64 bit Op system with no issues. If there is something I can research or provide off my system that might help diagnose the issue, I'm willing. But someone would have to tell me what it is that might be helpful and how to provide it. Just offering to help.

[MickJT]

I have sent a message to jdobbs describing this bug in detail. BD Rebuilder is only changing the AVC registry key to use ffdshow, and not any of the others. The easy solution is to use the Win 7 DS Filter Tweaker, and also edit the ffdshow settings with the configuration tool that comes with ffdshow. BD Rebuilder is also not changing any of the ffdshow settings either, despite saying it has.

It may be an issue just on 64bit. In any case, I have ran procmon while BD Rebuilder does its thing, and I can see that it is definitely not doing what it says it is.

[MickJT]

I figured i'll just post the contents of my private message here. There's no reason for it to be private other than its long length. It's 2 private messages separated by "------".

-----

I haven't bothered to really look into this bug for a long time now, but it's been this way since at least post 9903: http://forum.doom9.org/showthread.php?p=1452256

I got out procmon to have a look at what the problem is.

I run Windows 7 64bit. This means the 32bit codec registry settings are in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\DirectShow\Preferred and the 64bit codec settings are in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectShow\Preferred

BD-Rebuilder recommends using only a particular build of ffdshow-tryouts, and the 32bit edition. This is fine. I have no 64bit ffdshow-tryouts installed.

The Inspect tool checks 3 registry points for AVC / VC-1 & MPEG-2 (according to procmon)

AVC: {31435641-0000-0010-8000-00AA00389B71}
VC-1: {31435657-0000-0010-8000-00AA00389B71}
MPEG-2: {e06d8026-db46-11cf-b4d1-00805f6cbbea}

By default, on a clean setup (mine is), all 3 keys are set to use Microsoft's built in codecs, instead of ffdshow.

The string value for ffdshow show for those 3 keys is

{04FE9017-F873-410E-871E-AB91661A4EF7}

I know you know this already. I've searched through posts of yours.

When loading up BD-Rebuilder, it checks these 3 keys, the same as the Inspect.exe tool does.

A message appears.

BD Rebuilder: FFDSHOW Not Configured

It appears your Windows 7 System may not be configured for
use with FFDSHOW. BD Rebuilder can attempt to configure your
system for you. This involves making changes to the DirectShow
REGISTRY. Failure to do so may result in out-of-sync audio
or encode failures.

Would you like BD Rebuilder to do this for you?


Clicking "Yes" brings up a message.

Your Windows 7 system has been successfully configured
to use FFSHOW with BD Rebuilder.


Forgiving the typo (FFSHOW instead of FFDSHOW), this message is inaccurate.

BD Rebuilder only modifies one key. That key is {31435641-0000-0010-8000-00AA00389B71}, the AVC key.

Quitting BD Rebuilder and opening the Inspect tool shows that BD Rebuilder has indeed corrected the preferred codec for AVC, but left the others unchanged, resulting in the message to fix the issue every time BD Rebuilder is ran.

Procmon was used to confirm the behaviour of Inspect / BD Rebuilder.

All versions used when making this private message are the latest and/or required versions of the tools BD Rebuilder uses, as of this date, 16th March 2011.

---------

I'm going to just assume here that you've never encountered that bug before (even though it's persisted over a long time and and a fresh installation of Windows 7 64bit).

My guess is that it's writing the first registry key (AVC codec preferred filter), then somehow exiting the loop and not writing the other changes, because it is not writing the changes for ffdshow either (whether it is meant to, I don't know!).

I'm willing to be a test guinea pig.

--------

[jdobbs]

I have sent a message to jdobbs describing this bug in detail. BD Rebuilder is only changing the AVC registry key to use ffdshow, and not any of the others. The easy solution is to use the Win 7 DS Filter Tweaker, and also edit the ffdshow settings with the configuration tool that comes with ffdshow. BD Rebuilder is also not changing any of the ffdshow settings either, despite saying it has.

It may be an issue just on 64bit. In any case, I have ran procmon while BD Rebuilder does its thing, and I can see that it is definitely not doing what it says it is. Unfortunately, though, I tested it following your PM and from what I see your statement is incorrect. On both of my Win 7 systems (32 bit and 64 bit) it appears to be configuring everything correctly. I think it may be some issue (probably rights related) on your system. But, as always, I'll continue to test it.

[MickJT]

I do think it's the issue that people are reporting here. It is a freshly installed system. I am willing to be a test guinea pig if you want to give me a version with extra console debug output after it changes each key. I can easily verify in procmon itself that it is not even attempting to change any other registry keys.

I could post video proof too (of procmon/bd-rebuilder together). I'd rather just send the link in a private message though.

The problem with a debug version is it might say that it's changing each key, but procmon says different!

Edit: I can edit the key in regedit without any issue. As said, procmon shows that BD Rebuilder doesn't even attempt it. If it was a permissions issue, procmon would still show BD Rebuilder trying to change it. I have tried both "Run as Administrator" and without.

Perhaps those with this issue can use the filter tweaker or FF_RESET to put AVC back to the Microsoft filter. Then see whether BD-Rebuilder is able to at least change the AVC filter back to ffdshow.

Edit2: FF_RESET.BAT does work here. If I modify it myself (just some arbitrary values to verify it works) and run it as Admin, I do see all changes.

[jdobbs]

I do think it's the issue that people are reporting here. It is a freshly installed system. I am willing to be a test guinea pig if you want to give me a version with extra console debug output after it changes each key. I can easily verify in procmon itself that it is not even attempting to change any other registry keys.

I could post video proof too (of procmon/bd-rebuilder together). I'd rather just send the link in a private message though.

The problem with a debug version is it might say that it's changing each key, but procmon says different!

Edit: I can edit the key in regedit without any issue. As said, procmon shows that BD Rebuilder doesn't even attempt it. If it was a permissions issue, procmon would still show BD Rebuilder trying to change it. I have tried both "Run as Administrator" and without. The .BAT file is just removed after successful execution.

Perhaps those with this issue can use the filter tweaker or FF_RESET to put AVC back to the Microsoft filter. Then see whether BD-Rebuilder is able to at least change the AVC filter back to ffdshow.

Edit2: FF_RESET.BAT does work here. If I modify it myself (just some arbitrary values to verify it works) and run it as Admin, I do see all changes. The original changes are made exactly as FF_RESET.BAT does them only in reverse (with the FFDSHOW keys). The .BAT file is just removed after successful completion.

[MickJT]

Yes, but I can modify FF_RESET.BAT with the values needed to do it in "reverse-reverse", i.e set it up the way BD-RB needs it, and it works fine. Procmon is just showing me that in the BD-Rebuilder.exe process, no attempts are being made to alter anything except the AVC preferred filter, whether there's a permissions issue or not; It would still show up. Willing to run any tests you might have for me.

[jdobbs]

Yes, but I can modify FF_RESET.BAT with the values needed to do it in "reverse-reverse", i.e set it up the way BD-RB needs it, and it works fine. Procmon is just showing me that in the BD-Rebuilder.exe process, no attempts are being made to alter anything except the AVC preferred filter, whether there's a permissions issue or not; It would still show up. Willing to run any tests you might have for me. It is working for me, and it's been working for other users for a long time now as well -- that would seem to indicate it has to be something specific to your system. I can't imagine how it would work differently just because it is executed through a shell call via the O/S, though.

[MickJT]

It isn't specific to my system. Bokker is having the same issue, but you guided him through fixing it up manually. sbtuttle has the same issue, and couldn't be bothered with all the hard work to fix it up.

My HDD died recently and I simply installed Windows 7 64bit, fresh (no image restore), then ffdshow, Haali, AviSynth and BD-Rebuilder. There's nothing fancy on here. Again, procmon shows BD-Rebuilder isn't even attempting to fix up the other keys. So, whether it is something with my system or not, it must still be a bug. BD-Rebuilder should at least be trying, and it is successful at changing the AVC filter, but it doesn't try to change anything else other than that. It is able to read all 3 keys. It only tries writing one of them (AVC) when it's not set up correctly, and that works fine. So it's not failing at doing something, but actually not attempting it in the first place.

I do need to stress that this system is fresh. Plain Win 7 64bit install, Firefox, Haali, AviSynth, ffdshow, BD-Rebuilder, iTunes, VideoLAN. That's it. No virus checker, nothing. Oh, and AnyDVD HD but I only just put that on there today. I also installed Win 7 Service Pack 1.

Would you like me to send you a link to a full procmon log (nothing excluded from the list)?

Edit: Woah. Hold on, it appears to be working now. Double-checking.

I found the cause. Still a bug, sort of. Wait for an edit. Check next post.

[MickJT]

OK. The culprit is Win 7 DS Filter Tweaker. After running that, it does something that I can't detect that prevents BD-Rebuilder from setting the registry keys. BD-Rebuilder doesn't even make FF_CONFIGURE.BAT (I wish it didn't delete it, so I could view what was in it).

Here is where it gets weird. Open up regedit, and double-click on {31435641-0000-0010-8000-00AA00389B71}

Change it (the value inside the key, not the key itself) to something else (regedit won't save non-edits).

After that, it's fine, BD-Rebuilder can do its thing. The weird thing is, no matter whether it's the AVC, VC-1 or MPEG-2 codec you changed in Win 7 DS Filter Tweaker, it is the {31435641-0000-0010-8000-00AA00389B71} key (AVC) that must be re-saved before BD-Rebuilder is able to fix the VC-1 / MPEG-2 keys and all the ffdshow settings.

At least you know what to look for now jdobbs! Run the tweaker program. It won't mess anything up, I promise (well, other than present this bug/issue to you).

Remember it's not only Win 7 DS Filter Tweaker that may do something like this that prevents BD-Rebuilder from fixing it. Seeing as regedit (or FF_RESET.BAT) works to fix it so BD-Rebuilder can fix the settings again, i'm a bit baffled. Is it a permissions issue or not? Hmm.

[jdobbs]

OK. The culprit is Win 7 DS Filter Tweaker. After running that, it does something that I can't detect that prevents BD-Rebuilder from setting the registry keys. BD-Rebuilder doesn't even make FF_CONFIGURE.BAT (I wish it didn't delete it, so I could view what was in it).

Here is where it gets weird. Open up regedit, and double-click on {31435641-0000-0010-8000-00AA00389B71}

Change it (the value inside the key, not the key itself) to something else (regedit won't save non-edits).

After that, it's fine, BD-Rebuilder can do its thing. The weird thing is, no matter whether it's the AVC, VC-1 or MPEG-2 codec you changed in Win 7 DS Filter Tweaker, it is the {31435641-0000-0010-8000-00AA00389B71} key (AVC) that must be re-saved before BD-Rebuilder is able to fix the VC-1 / MPEG-2 keys and all the ffdshow settings.

At least you know what to look for now jdobbs! Run the tweaker program. It won't mess anything up, I promise (well, other than present this bug/issue to you).

Remember it's not only Win 7 DS Filter Tweaker that may do something like this that prevents BD-Rebuilder from fixing it. Seeing as regedit (or FF_RESET.BAT) works to fix it so BD-Rebuilder can fix the settings again, i'm a bit baffled. Is it a permissions issue or not? Hmm. So how does an issue with "Win 7 DS Filter Tweaker" suddenly become my problem to fix?

[MickJT]

So how does an issue with "Win 7 DS Filter Tweaker" suddenly become my problem to fix?

Well, clearly Win7DSFilterTweaker does something, but it could have been something else, who knows.

When someone has a problem whereby BD-Rebuilder does not set the filters and ffdshow settings but says it did, then this is just 1 way in which this problem could be caused.

Forget Win7DSFilterTweaker was used. Fact is, BD-Rebuilder said it did something which it didn't. This is one way you can replicate the problem, that is all. Just one way. It could be something else for other people, but nevertheless this is one way for you to replicate the issue.

[jdobbs]

Well, clearly Win7DSFilterTweaker does something, but it could have been something else, who knows.

When someone has a problem whereby BD-Rebuilder does not set the filters and ffdshow settings but says it did, then this is just 1 way in which this problem could be caused.

Forget Win7DSFilterTweaker was used. Fact is, BD-Rebuilder said it did something which it didn't. This is one way you can replicate the problem, that is all. Just one way. It could be something else for other people, but nevertheless this is one way for you to replicate the issue. You have posted this now in two different threads and I have answered you in both. This is NOT AN ISSUE WITH BD REBUILDER and no matter how many times you cross-post it the bottom line is that even if I wanted to (which I don't) I cannot fix an issue in someone elses software. Send your bug report to them. :mad:

[MickJT]

You have posted this now in two different threads and I have answered you in both. This is NOT AN ISSUE WITH BD REBUILDER and no matter how many times you cross-post it the bottom line is that even if I wanted to (which I don't) I cannot fix an issue in someone elses software. Send your bug report to them. :mad:

Lets move this to the bug reporting thread. As said there, the issue is that BD-Rebuilder says it fixed something which it didn't. The cause that makes BD-Rebuilder do that, is irrelevant. Fact is, it is possible for something to make BD-Rebuilder exhibit this behaviour.

Like a buffer overflow which can be used to inject code on unsecure platforms. You don't say "I won't fix it, the solution is to not use that tool to overflow the buffer". Clearly there would be a bug that allows the buffer overflow to occur!

[jdobbs]

@MickJT

You have gotten your answer and now you're talking nonsense for which I have not time. Asking me to fix an issue caused by someone elses software is about as silly as it gets. If you can't understand that, then I have to assume you won't understand any further explanation either.

As moderator I am instructing you to cease posting on this subject. It is off topic. You have violated rules 3, 8, 10, and now rule 16. Continue and you will receive strikes and/or be banned.

[Siddus]

I have tried 20 times now to install BD-Rebuilder on my windows 7 64 bit ultimate (with sp1) and I have followed all the suggested ways to install (uninstall everything, reboot and reinstall).
Run REG_MSCOMCTL.BAT as admin, and then run BD-Rebuilder.exe as admin which gives this at every startup:
"It appears your windows 7 system may not be configured for
use with FFDSHOW. BD-Rebuilder can attempt to configure your
system for you. This involves making changes to the DirectShow
REGISTRY. Failure to do so may result in ouf-of-sync audio
or encode failures

Would you like BD-Rebuilder to do this for you ?"
I always click ok..

And this is what the inspect.exe give as result:
- Windows Version: 6.1 [7601]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.11.96.14, Ok
- FFDSHOW: 3882, Ok
- WIN7 preferred AVC CODEC: Not Set correctly
- WIN7 preferred VC-1 CODEC: Not Set correctly
- WIN7 preferred MPEG2 CODEC: Not Set correctly
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libmpeg2": Ok
- FFDSHOW AVC set to "ffmpeg-mt": Ok
- BD Rebuilder v0.38.0.4, Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
The versions I am using is the latest recomended at http://forum.doom9.org/showthread.php?t=143716 (BD-Rebuilder BD-RBV03804)
and I have followed all the suggested settings on that page.
I have only a few burn software installed (dvdfab, alcohol-soft and nero) + media player classic HC and I don't understand why BD-Rebuilder
can't make the "WIN7 preferred CODEC" settings ??
I have also tried to login as administrator to remove the need for "right click and run as admin" and still no luck..
How can I make these settings manually (if there is a way)??
/Siddus

[Capsbackup]

Have you tried jdobbs suggestion, found on page 2 of this thread, from post # 22 and continue reading?

[Siddus]

I have tried all suggestions found here..
But the problem is solved now, I managed to save the FF_CONFIGURE.BAT before it disappeared and made these changes manually (the only way to get it to work), so now it's up and running..
/Siddus

[SLOVEHEART]

(deleted words)...I can't seem to get it to even start up, I get this error:
"Component MSCOMCTL.OCX or one of it's dependencies not correctly registered: a file is missing or invalid"
I try the fix - "Look in the BD-RB folder. There is a .BAT file called "REG_MSCOMCTL.BAT" -- simply right click onit and run it as administrator."
But then I get this - The Module MSCOMCTL.OCX failed to load... So this does not work for me...(deleted words)


What I have had to end up doing to avoid the lang.xml error or others, is to use the Windows Command Line Processor (old DOS window), and start this w/ right click - Run as Administrator - then navagate to BD Rebuilder's directory (useful trick - when changing directories - type first letter of wanted directory (on target drive) then use 'Tab' key- it will jump through all directories starting w/ that letter, one by one, until your desired one pops up - then continue) once inside BD Rebuilder - locate "REG_MSCOMCTL.BAT" (tab key works also for file names) - then simply run the batch file - no issues - for me at least...

Cheers...

[monstirz]

I clicked on BD-Rebuilder and then right clicked Administrator and I am still getting the mscomctl.ocx error. I offloaded the software to recycle bin and re installed BD-Rebuilder and the reg..,bat file was right clicked on first and ran as administrator and still got the same error message. I even have this as sucessfully loaded in in cmd under regserver32. Still the same error message..,Any cures for this in 32 bit Win 7? Desperate in Vegas.

[jdobbs]

Right click on "REG_MSCOMCTL.BAT" in the BD Rebuilder folder and "Run as Administrator". Normally MSCOMCTL is registered on Windows 7 as a part of the Win7 installation -- but on rare occasions it isn't there. I've never been able to figure out why.

[cinephage]

Right click on "REG_MSCOMCTL.BAT" in the BD Rebuilder folder and "Run as Administrator". Normally MSCOMCTL is registered on Windows 7 as a part of the Win7 installation -- but on rare occasions it isn't there. I've never been able to figure out why.

Didn't work for me: failed...

[Capsbackup]

Didn't work for me: failed...

You also need to right click on BDRB.exe and select "Run as Administrator". ( Just the 1st time ) :)
I would recommend placing the unzipped folder of BD-RB on the desktop or directly in C:, not in the Windows Program folder.

[cinephage]

You also need to right click on BDRB.exe and select "Run as Administrator". ( Just the 1st time ) :)
I would recommend placing the unzipped folder of BD-RB on the desktop or directly in C:, not in the Windows Program folder.

Thanks. It did work.

[duftopia]

OK. The culprit is Win 7 DS Filter Tweaker. After running that, it does something that I can't detect that prevents BD-Rebuilder from setting the registry keys. BD-Rebuilder doesn't even make FF_CONFIGURE.BAT (I wish it didn't delete it, so I could view what was in it).

Here is where it gets weird. Open up regedit, and double-click on {31435641-0000-0010-8000-00AA00389B71}

Change it (the value inside the key, not the key itself) to something else (regedit won't save non-edits).

After that, it's fine, BD-Rebuilder can do its thing. The weird thing is, no matter whether it's the AVC, VC-1 or MPEG-2 codec you changed in Win 7 DS Filter Tweaker, it is the {31435641-0000-0010-8000-00AA00389B71} key (AVC) that must be re-saved before BD-Rebuilder is able to fix the VC-1 / MPEG-2 keys and all the ffdshow settings.

At least you know what to look for now jdobbs! Run the tweaker program. It won't mess anything up, I promise (well, other than present this bug/issue to you).

Remember it's not only Win 7 DS Filter Tweaker that may do something like this that prevents BD-Rebuilder from fixing it. Seeing as regedit (or FF_RESET.BAT) works to fix it so BD-Rebuilder can fix the settings again, i'm a bit baffled. Is it a permissions issue or not? Hmm.

I have the same problem and bd-rebuilder cannot get around the vc-1 issue due to it, I can't seem to fix the registry, ffdshow changes the parms but it gets changed back and so I went with alternative methods to get the issue resolved.

YES win 7 64 bit issues is the problem, but it would be nice to get a simple fix for it

Duf

[MrVideo]

My curiosity has done me in!
I wanted to see if I could run Windows 7 on my I7 920 computer, and after running the Win 7 update advisor, it warned me there could be some conflicts. The challenge was on.
I decided to try the Ultimate edition RC, since it was free, and if I did not like it or it did not seem worth the upgrade price, it would expire soon enough and only a few hours would be waisted. ( waisted plenty in my time! ):)
Well, all installed fine, and after searching around for updated drivers for some hardware, all was a go.
Now trying BD-RB, all is not so well.:o
I can't seem to get it to even start up, I get this error:
"Component MSCOMCTL.OCX or one of it's dependencies not correctly registered: a file is missing or invalid"
I try the fix - "Look in the BD-RB folder. There is a .BAT file called "REG_MSCOMCTL.BAT" -- simply right click onit and run it as administrator."
But then I get this - The Module MSCOMCTL.OCX failed to load... So this does not work for me.
Can BD-RB run with Windows 7 RC?
How else can you get rid of this MSCOMCTL.OCX REG issue just to get BD-RB to start?
After reading back numerous pages, I can't seem to find out what to do next. Any help is sure appreciated.:confused:

EDIT:
OK, I got it to work by right clicking on BD_Rebuilder and selecting "Run as Administrator", which it then set up ffdshow for me, and now it starts up.
Off to try out a backup! :p
I had to reinstall M$ because I got in my new Gigabyte mobo Monday. I hate M$ security. I have to go find all the things I found before to stop M$ from this or that file change from happening.

In any event, right-clicking on "REG_MSCOMCTL.BAT" and running as administrator will always fail, because when run as administrator, the regsvr32 program is started from within the c:\Windows\system32 directory. MSCOMCTL.OCX is not in that location. If you right-click on "REG_MSCOMCTL.BAT" and click on OPEN instead, it will fail because you aren't admin. Which is fracking stupid because I am the only user on the system. Damn M$ permissions. We're M$ and we are trying to protect you. :mad:

So, I did the trick of right clicking on BD_Rebuilder and selecting "Run as Administrator." That worked. I think there should be text added to the readme for doing this trick in the installed location. Or, an improved BAT file that can get at the file in the OCX file in the installed location.

I do not remember having this bad of an issue the first time I installed it. Maybe I had frack'd with the permissions before installing BDRB.

[Ch3vr0n]

check the BOLD NOTE under item 9 in the setup instructions :p

Note to Windows 7, Windows 8, and Windows 10 Users: The first time (and only the first time) you run BD Rebuilder, you may have to "Run As Administrator". This is necessary so BD-RB can make CODEC preference changes in the Windows Registry.

No need to add when it's already there :p

[MrVideo]

Argh!!! And to think I read the readme before posting and still missed that paragraph. :o