• AnyStream is having some DRM issues currently, Netflix is not available in HD for the time being.
    Situations like this will always happen with AnyStream: streaming providers are continuously improving their countermeasures while we try to catch up, it's an ongoing cat-and-mouse game. Please be patient and don't flood our support or forum with requests, we are working on it 24/7 to get it resolved. Thank you.

Becky

rictheyardi

New Member
Thread Starter
Joined
Aug 31, 2007
Messages
3
Likes
0
Trying to backup Becky blu ray dvd but it not even recognized in the drive..:(
 
Disable anydvd for a moment, does windows see the disc now? If not, it's not an anydvd problem but a drive/disc problem. If the drive doesn't detect the disc, it can't tell anydvd there's something to decrypt.

Sent from my Pixel 3 XL using Tapatalk
 
I'm having the same issue of not recognizing that a disk is in the drive (Windows 10 Pro)... (BUT!!!icon_biggrin.gif)....

Drives:
ASUS BW-16D1HT - Does NOT work icon_sad.gif
LG-WH16NS60 - Does NOT work icon_sad.gif
LG-BU40N - Does NOT work icon_sad.gif
BUT.... the Pioneer - BDR-XD05 - DOES work! (Old-School Drive; 2015) icon_biggrin.gif

I wonder what is different with this drive/hardware/disk???
 
I'm having the same issue of not recognizing that a disk is in the drive (Windows 10 Pro)... (BUT!!!View attachment 52340)....

Drives:
ASUS BW-16D1HT - Does NOT work View attachment 52341
LG-WH16NS60 - Does NOT work View attachment 52342
LG-BU40N - Does NOT work View attachment 52343
BUT.... the Pioneer - BDR-XD05 - DOES work! (Old-School Drive; 2015) View attachment 52344

I wonder what is different with this drive/hardware/disk???
Why not post some AnyDVD logfiles?
 
Why not post some AnyDVD logfiles?
Sorry... I thought it was a hardware issues not an ANYDVD software issue.
Log file attached....
 

Attachments

  • AnyDVD_8.4.9.2_Info_F_BECKY_BDCB380E_30A85480.ziplog
    122.4 KB · Views: 5
The latest stable version is 8.4.9.0, I avoid using beta software. 8.4.9.2 is in beta.
I dislike the use of the term "stable version", as it insinuates, that beta versions are somehow "unstable", which is nonsense.
In most cases, beta versions simply have some new or modified feature that needs testing and may be in a sense "unstable" - while the rest of the software works as always.

The beta state of the current version is of no consequence to the matter in question here.
Plus it's fine if you decide to avoid beta versions - but if everyone held that position, release versions would never become "stable".
 
Last edited:
Sorry... I thought it was a hardware issues not an ANYDVD software issue.
Log file attached....
According to the log, only a "Ven_WD&Prod_Virtual_CD_260D&Rev_2003" drive (whatever this is?) is attached. Apart from the Pioneer, of course.

How are
ASUS BW-16D1HT
LG-WH16NS60
LG-BU40N

connected?

EDIT:
And you're right, it is not an AnyDVD issue. Just trying to help you troubleshoot.
 
I dislike the use of the term "stable version", as it insinuates, that beta versions are somehow "unstable", which is nonsense.
In most cases, beta versions simply have some new or modified feature that needs testing and may be in a sense "unstable" - while the rest of the software works as always.

The beta state of the current version is of no consequence to the matter in question here.
Plus it's fine if you decide to avoid beta versions - but if everyone held that position, release versions would never become "stable".
Ok, well, thank you for explaining that.
 
According to the log, only a "Ven_WD&Prod_Virtual_CD_260D&Rev_2003" drive (whatever this is?) is attached. Apart from the Pioneer, of course.

How are
ASUS BW-16D1HT
LG-WH16NS60
LG-BU40N

connected?

EDIT:
And you're right, it is not an AnyDVD issue. Just trying to help you troubleshoot.

I only have one drive at a time connected. The disk is only recognized by the Pioneer BDR-XD05 drive (MFD March 2015). I used someones newer Pioneer BDR-XD05 drive with a MFD of July 2019 and that worked also. I used the Pioneer drive and original disk to create the log file (no virtual ISO file/drive used). All the other drives just keep hunting with the laser sliding back and forth for about a minute... then saying no disk found. Also my ASUS and LG-WH16NS60 have been flashed. Thoughts???
 
I'm having the same issue with 2 different copies of the disk. I have 2 BD drives AnyDVD 8.9.4.0 latest patches to Win 10
LG HL-DT-ST BD-RE BH16NS40
ASUS BW-16D1HT USB Device

Can't produce log because disc is not seen.

Disk is seen on older machine with latest Win 10 Patch Anydvd 8.9.4.0
LG DT-DT-ST BD-RE BH16NS40

There has to be some software variation but drivers seem to match.
 
I'm having the same issue with 2 different copies of the disk. I have 2 BD drives AnyDVD 8.9.4.0 latest patches to Win 10
LG HL-DT-ST BD-RE BH16NS40
ASUS BW-16D1HT USB Device

Can't produce log because disc is not seen.

Disk is seen on older machine with latest Win 10 Patch Anydvd 8.9.4.0
LG DT-DT-ST BD-RE BH16NS40

There has to be some software variation but drivers seem to match.
You can produce logs anyway. But if Windows doesn't see the discs, AnyDVD won't either.
 
I have the same issue. Here is the log.
 

Attachments

  • AnyDVD_8.4.9.0_Info_D_BECKY.ziplog
    109 KB · Views: 1
I have the same issue. Here is the log.

actually no you don't. The volume name is the same, but your logfile status information specifically mentions "WARNING: Read errors on disc!"

16.55s: read sectors failed, sense 4:3e:2 // **** TIMEOUT ON LOGICAL UNIT
16.55s: tries 9 retry 3922704 to 3922720
26.80s: read sectors failed, sense 4:3e:2 // **** TIMEOUT ON LOGICAL UNIT
26.80s: tries 8 retry 3922704 to 3922720
36.59s: read sectors failed, sense 4:3e:2 // **** TIMEOUT ON LOGICAL UNIT
36.59s: tries 7 retry 3922704 to 3922720
45.36s: read sectors failed, sense 4:3e:2 // **** TIMEOUT ON LOGICAL UNIT
45.36s: tries 6 retry 3922704 to 3922720
54.27s: read sectors failed, sense 4:3e:2 // **** TIMEOUT ON LOGICAL UNIT
54.27s: tries 5 retry 3922704 to 3922720
63.47s: read sectors failed, sense 4:3e:2 // **** TIMEOUT ON LOGICAL UNIT
63.47s: tries 4 retry 3922704 to 3922720
73.92s: read sectors failed, sense 4:3e:2 // **** TIMEOUT ON LOGICAL UNIT
73.92s: tries 3 retry 3922704 to 3922720
83.80s: read sectors failed, sense 4:3e:2 // **** TIMEOUT ON LOGICAL UNIT
83.80s: tries 2 retry 3922704 to 3922720
93.48s: read sectors failed, sense 4:3e:2 // **** TIMEOUT ON LOGICAL UNIT
93.48s: tries 1 retry 3922704 to 3922720
106.34s: read sectors failed, sense 4:3e:2 // **** TIMEOUT ON LOGICAL UNIT
 
Back
Top