Windows 7 Explorer cannot see UDF discs - please help!

[Nine Iron]

I'm having a problem with my LG BH08LS20 BD-R drive.

When I try to read UDF discs (i.e. standard "file and folder" structure), Windows reports an unrecognized file system. Nero can write UDF Blu-Rays fine, and VLC can read DVD movies fine, but reading of UDF discs of either type is a no-go. The drive works properly in my father's computer, by the way, and is running the latest firmware, and I have the latest drivers on mine. I've tried two different SATA ports and two different cables.

Only changes I've made are an installation of Isobuster (which I since uninstalled) and a recent Windows update. I strongly suspect that my W7 UDF reader is damaged, or there is a conflict - does this sound plausible? If so, does anybody have any ideas on how to restore the native Windows UDF, or replace it?

Please help me ASAP if you are able - I really don't want to do a re-install of Windows if I can avoid it.

 

[kbalaz]

look for an update for your intel Sata AHCI Controller.

 

[Nine Iron]

look for an update for your intel Sata AHCI Controller.

Windows can't find anyting newer than what I've got on, but there are newer drivers on the MSI support page. However, when I install them, the install doesn't "take", and I'm left with the original drivers.

Edit - I just used my motherboard driver CD to attempt to roll back to the original drivers, but the installer reported a different driver version than the Windows device manager.

Odd. Could it be a BIOS problem?

 

[Estacado7706]

What's on the discs? Have you burned them yourself? By any chance with Windows XP and Nero? (If all UDF disks show this problem diregard this question)

Can you see the contents with isobuster?

There is an udf driver in windows/system32. COuld you check the version and perhaps test a different one?

One thing that sometimes helps: Open the Windows Media Player and after this, open your explorer and check. Some routines called by MP are said to bypass this error. (Not kidding. Even MS proposes this as a workaround: http://support.microsoft.com/kb/321640/en-us)

 

[Nine Iron]

What's on the discs? Have you burned them yourself? By any chance with Windows XP and Nero? (If all UDF disks show this problem diregard this question)

Can you see the contents with isobuster?

There is an udf driver in windows/system32. COuld you check the version and perhaps test a different one?

One thing that sometimes helps: Open the Windows Media Player and after this, open your explorer and check. Some routines called by MP are said to bypass this error. (Not kidding. Even MS proposes this as a workaround: http://support.microsoft.com/kb/321640/en-us)

Answered in order asked:

1. Some burned on XP, most on W7.

2. Isobuster did show the contents (before I uninstalled it, that is).

3. I've been trying to reinstate the UDF reader, or find an alternative one, since the problem started, and it's a complete ball-ache - can't find any installers for it.

(4. I did read about the WMP workaround - I couldn't believe MS themselves were reduced to that, but there we are!)

Just installed the latest SATA/AHCI driver (I was looking at the individual PCI-e ports in Device Manager - my bad, @kbalaz), and I got a good read on a few UDF discs - I'll take it through a few restarts and see if she holds up...

 

[Estacado7706]

Answered in order asked:

1. Some burned on XP, most on W7.

2. Isobuster did show the contents (before I uninstalled it, that is).

3. I've been trying to reinstate the UDF reader, or find an alternative one, since the problem started, and it's a complete ball-ache - can't find any installers for it.

(4. I did read about the WMP workaround - I couldn't believe MS themselves were reduced to that, but there we are!)

Just installed the latest SATA/AHCI driver, and I got a good read on a few UDF discs - I'll take it through a few restarts and see if she holds up...

Good to know that the driver worked for you.

If the XP ones stay unreadable don't mind. XP itself could do all UDF Versions, so Nero Extensions kicked in and this will often be a problem.
And yes, the workaround is strange, especially that it is from the official MS knowledge base

 

[Nine Iron]

I wonder why the driver suddenly stopped being up to the job... I only noticed the problem today because I tried to play a Blu-Ray I'd burnt (to make sure it'd come out right), but it could have started any time since I last used a UDF... corrupted drivers, maybe? Or a Windows update knocked the current ones out of kilter?

Anyway, seems to be resolved, and props to all responders (especially @kbalaz).

 

[kbalaz]

I wonder why the driver suddenly stopped being up to the job... I only noticed the problem today because I tried to play a Blu-Ray I'd burnt (to make sure it'd come out right), but it could have started any time since I last used a UDF... corrupted drivers, maybe? Or a Windows update knocked the current ones out of kilter?

Anyway, seems to be resolved, and props to all responders (especially @kbalaz).

you are very welcome, that is why this forum is so great. Lots of people who have had to deal with similar issues in the past. Saves the headache of looking around for the right answer. Glad it worked in your case.

 

[Nine Iron]

Another (possible) issue?

Well, the UDF read is back, but something else has started to happen that's bugging me:

Occasionally, when I put a disc - of any type - into the drive, it takes a long time (sometimes up to a minute) for Windows to recognize the content. It then works fine, but Explorer sometimes gets the disc size wrong.

Then, after I remove the disc from the drive, Windows Explorer "remembers" the disc - instead of immediately killing the contents window and showing the empty drive icon in My Computer - for a very long time; to get the empty drive icon back I have to eject the drive via Windows, or wait.

Any ideas what could be going on here? It seems to start happening after three or four discs, and the only change I've made is that SATA/AHCI driver update a few days ago. I don't think it's the BD-R drive itself that's at fault, because that wouldn't explain the Windows "retention" of ejected discs...

------------------------------------------

EDIT - OK, that was scary: my storage hard drive disappeared for a moment, there. Shut down, moved it to a different SATA port, restart, and it's back. I think something's not right with my board, here...