Strange DVD problem on W7 PCs

[Gazdok]

I have just bought a second hand replacement PC for my son with good scpecs and a wiped and freshly installed W7 home premium 64 bit OS. The seller said the DVD RW was working and is being recognized by the BIOS but W7 does not address it properly.
It is an Optiarc DVD RW Ad-5260s. It appears with a yellow triangle and a code28 in Device manager.
No problem ....
I just swap it for one in my own PC which is a Phillips DROM 6316 which has always been working fine was recognized by my OS - W7 ultimate 64 bit.
At first the W7home premium DID read the DVDs but then it marked it in the same way as the Optiarc with a yellow triangle and a code 28.
The optiarc however is recognized without problem in my PC. The one big difference - if I remember correctly - is the the W7 ultimate names it SCSI. Even forcing the W7 ultimate OS to look for a new driver does not cause a problem.
Why should W7 home premium have problems recognizing DVD drives. The driver files are present on the W7 home premium PC.

 

[Boozad]

Try deleting the UpperFilters\LowerFilters registry entry.

To start Registry Editor Click Start, type regedit in the quick search, and then click the regedit icon in the search results. Registry Editor starts.

1. In Registry Editor expand My Computer, and then expand HKEY_LOCAL_MACHINE.
2. Expand SYSTEM
3. Expand ControlSet001
4. Expand Control
5. Expand Class
6. Search for the key {4D36E965-E325-11CE-BFC1-08002BE10318} and left click on it, bringing the values up on the right.
In the right hand pane (topic area), you may have Upperfilters, Lowerfilters or both. Click UpperFilters if you have it and delete it, if you have LowerFilters delete this as well. If you only have one of the two, just delete that one, don't worry about the one that isn't there.

 

[Gazdok]

I had a look in there as well when the optiarc DVD was in the home premium PC and I did not have any filters at all.

 

[Boozad]

Apologies, I read the error as Code 19 instead of Code 28. Have you tried installing drivers for the drive on the PC you're fitting it in?

 

[ComputerGeek]

Try deleting the UpperFilters\LowerFilters registry entry.

To start Registry Editor Click Start, type regedit in the quick search, and then click the regedit icon in the search results. Registry Editor starts.

1. In Registry Editor expand My Computer, and then expand HKEY_LOCAL_MACHINE.
2. Expand SYSTEM
3. Expand ControlSet001
<snip>

Hi Boozad

"ControlSet001" is a Windows backup of the CurrentControlSet key. (e.g. If you select a "Restore Last Good Configuration" Windows restores one of the ControlSetnnn backups.

One needs to delete filters from the current Control key. To do so, one should modify CurrentControlSet.


/* EDIT */
@Gadzok
When you checked if any filters were installed did you check using Device Manager? See HERE (that's a simple and easy way to assure you're also checking the right registry entry)

I'd also check what version of firmware is installed and if any firmware upgrade available. If you google the NeroInfoTool it'll tell you the current firmware version

/* EDIT 2 */
p.s. A code 28 is odd for a standard device like a DVD. Also verify these files exist:
> C:\Windows\inf\cdrom.inf
> C:\Windows\inf\cdrom.pnf
> C:\Windows\system32\cdrom.sys

 

[Boozad]

Try deleting the UpperFilters\LowerFilters registry entry.

To start Registry Editor Click Start, type regedit in the quick search, and then click the regedit icon in the search results. Registry Editor starts.

1. In Registry Editor expand My Computer, and then expand HKEY_LOCAL_MACHINE.
2. Expand SYSTEM
3. Expand ControlSet001
<snip>

Hi Boozad

"ControlSet001" is a Windows backup of the CurrentControlSet Key. (e.g. If you select a "Restore Last Good Configuration" Windows restores one of the Control backup keys.

One needs to delete filters from the current Control key. To do so, one should modify CurrentControlSet.

Understood. That fix has actually worked in the past though, more than once.

 

[ComputerGeek]

OK.

Just wanted to point out the recommended method in Microsoft documentation is always editting current key ( the CurrentControlSet key ).

HERE's one example.

Was just my 2cents (or maybe just 1 1/2 cent worth )

 

[Gazdok]

Thanks for the replies.
The problem was that the installation - for whatever reason - has not left a "cdrom.inf" in Windows/inf. Copied it over from another PC and the drive installed without problem.