Hey folks,

Recently the new Windows 10 update 1809 was released for a while, before it was withdrawn by Microsoft. My PC was updated, and while I didn't notice any problems with data loss, I noticed a problem today. And it had to do with our beloved DVD Profiler!

Some time ago, I bought a bunch of new Criterion discs, including the Letters From Fontainhas box (715515053013). Hadn't added it to my collection, so I did, and started checking the disc. It had another disc id. OK... that can happen. And then the other 3 discs gave different disc ids too. Huh....

Checked a few other old Criterion discs. Also different from what's currently in the database!

OK, this is a serious problem. Could it be Windows 10, Bitdefender, maybe even iTunes or Spotify? I started tracing it back, and reverted to Windows 10 build 1803, and luckily the problem was solved. 

I will definitely monitor any new Windows 10 updates, and post updates here. Luckily I haven't submitted any new profiles with Windows 10 build 1809, but there may be users who did. If you have this build installed, check disc ids for some of your older titles.

If the disc id matches:  .
If it doesn't match, go back to build 1803, by going to your PC settings -> Update & Security -> Recovery -> Go back to an earlier build.

I hope I'm the only one who has had this problem!

Cheers,
Marcel

checked two blurays and the disc id which is created seems correct. (one a disc with id in the profile, one which got detected in the add disc dialog per id)

Hey folks,

I found out what's the cause of the disc id error on my drive in Windows 10 update 1809: It's a different cdrom.sys driver.

The previous cdrom.sys driver, version 10.0.17134.137, worked perfectly with the current DVD Profiler database. I checked about 10 DVDs with different regions and localities, and all were found when I used the 'Add by inserted disc' feature.

The current cdrom.sys driver is version 10.0.17763.1, and this one generates a different disc id. The same 10 DVDs are not found with the 'Add by inserted disc' feature.

Here's another example of a DVD I just bought (Brimstone: 5414937033386). Added disc id before and after the update.

Main Feature (10.0.17134.137) : 070F4732A4854631 [Brimstone]
Main Feature (10.0.17763.1) : CEDD2A15A59E9502 [Brimstone]

Unfortunately it's not possible to roll back this particular driver to an earlier version, and I'm now stuck with it. For the time being, I'm not going to contribute disc ids to the database.

Note that I'm only checking DVDs. I don't collect blu-ray or UHD, and my computer only has a DVD drive.

Can anyone else verify this? I'm going to put it in a support ticket too, but I'm not very confident about a follow up from Invelos.

Interesting.  I have the newer cdrom.sys driver mentioned above and I tested a few (much) older discs and the Disc ID came back the same as the old.

What the... rdodolak is correct.
This behaviour is very strange. I might be wrong but I remember that, long ago, with AnyDVD enabled, you would get a different ID...

Quoting Elwood Blues:

Quote:
What the... rdodolak is correct.
This behaviour is very strange. I might be wrong but I remember that, long ago, with AnyDVD enabled, you would get a different ID...

I tried this on a Windows 7 box too and can't replicate this behavior w/ or w/o AnyDVD.  So, it must have something specific with the cdrom.sys driver on Windows 10, AnyDVD and DVD Profiler.

Quoting mediadogg:

Quote:
I switched to DVDFab Passkey some time ago.

But in this case the correct disc ID is received when AnyDVD is enabled so, I wonder if that has something to do with the DVD Profiler fix.  When it's disabled the wrong disc ID is received.

Quoting rdodolak:

Quote:
I did some additional testing and this only seems to affect DVDs, but here is the kicker.

I also have AnyDVD and when AnyDVD is disabled I get a different Disc ID.  However, when it is enabled I get the same Disc ID as what is listed in the database.

Huh.

Just tested it with the aforementioned Brimstone DVD, and indeed, the original disc id shows up: 070F4732A4854631 [Brimstone] 

Same problem here. Just got a new Windows 10 PC. Several Disc IDs appeared wrong. Checked by running them through the aformentioned AnyDVD and, indeed, it corrects it.