BEE - Revision history

>Deterous at 08:36, 6 April 2026

2026-04-06T08:36:17Z

← Older revision		Revision as of 08:36, 6 April 2026
Line 117:		Line 117:
	- I do not know the exact date drives started being produced with BEE, but it may have been around 2011. Regardless, just check whether your drive has BEE via the above method to be sure.		- I do not know the exact date drives started being produced with BEE, but it may have been around 2011. Regardless, just check whether your drive has BEE via the above method to be sure.

	'''2. Dump with a libredrive compatible drive~~, like one with ribshark's modified ASUS~~ firmware, after having opened MakeMKV once with that drive, and said drive not having been unpowered long enough to clear its memory. ~~While BEE is still enabled in ribshark's firmware, the libredrive microcode stuff isn't patched out, and so as~~ long as you open ~~makemkv~~, it~~'ll~~ (among other things) disable the drive's BEE.'''		'''2. Dump with a libredrive compatible drive (OmniDrive or any MK firmware), after having opened MakeMKV once with that drive, and said drive not having been unpowered long enough to clear its memory. As long as you open (and then close) MakeMKV before dumping, it will (among other things) disable the drive's BEE.'''

	- FindVUK will still tell you that your drive has BEE, but will still give you proper AACSkeys dumps as long as you've disabled BEE via makeMKV before running it. DIC/redumper/etc will also still give you good dumps as long as you've disabled BEE via makeMKV before running them. If you want to be sure, it's always good to test BEE dumps via VLC, as described below.		- FindVUK will still tell you that your drive has BEE, but will still give you proper AACSkeys dumps as long as you've disabled BEE via makeMKV before running it. DIC/redumper/etc will also still give you good dumps as long as you've disabled BEE via makeMKV before running them. If you want to be sure, it's always good to test BEE dumps via VLC, as described below.

>Pelago: Some tidying, and splitting into sections

2025-07-10T21:22:59Z

Some tidying, and splitting into sections

← Older revision		Revision as of 21:22, 10 July 2025
Line 1:		Line 1:
	~~A relative minority of~~ BD-Video discs ~~have~~ Bus Encryption Enabled~~, or BEE~~. ~~You're relatively unlikely to encounter this on~~ BD-~~Video discs that~~ are ~~redump~~-~~eligible~~, ~~as BEE was mostly used for more traditional movie releases~~. ~~However, some redump~~-~~eligible~~ discs ~~do stll~~ have ~~it; additionally, all UHD discs have BEE, so if any are made that can be submitted to redump,~~ BEE ~~will have to be dealt with as well~~.		For BD-Video discs, BEE stands for Bus Encryption Enabled. Most BD-ROM drives are BEE-capable, but this can be disabled. Some BD-Video discs have BEE.

	There are various ways to check if your disc has BEE, but the easiest, given ~~this~~ guide already recommends installing FindVUK, is just to run FindVUK - AACSkeys.bat and check what it outputs for the disc you're trying to dump. Example relevant section output of a disc ''with'' BEE, on a drive that has BEE:		You're relatively unlikely to encounter this on BD-Video discs that are redump-eligible, as BEE was mostly used for more traditional movie releases. However, some redump-eligible discs do have it. Additionally, all UHD discs have BEE, so if any are made that can be submitted to redump, BEE will have to be dealt with for these discs too.

			== Checking to see if your disc has BEE ==

			There are various ways to check if your disc has BEE, but the easiest, given the [[BD-Video Key Extraction]] guide already recommends installing FindVUK, is just to run FindVUK - AACSkeys.bat and check what it outputs for the disc you're trying to dump. Example relevant section output of a disc ''with'' BEE, on a drive that has BEE:

	<pre>		<pre>
Line 32:		Line 36:
	"Disc-BusEncEnabled >1<" means that your disc has BEE; as seen here, there are various other indications.		"Disc-BusEncEnabled >1<" means that your disc has BEE; as seen here, there are various other indications.

	If you're not sure if a disc you submitted in the past has BEE, you can also check the .xml generated by FindVUK to see if it has BEE. If the disc does have BE, the xml will contain "<BusEncryptionEnabled>1</BusEncryptionEnabled>". If the disc does not have BEE, the xml will contain "<BusEncryptionEnabled>0</BusEncryptionEnabled>"		If you're not sure if a disc you submitted in the past has BEE, you can also check the .xml generated by FindVUK to see if it has BEE. If the disc does have BEE, the xml will contain "<BusEncryptionEnabled>1</BusEncryptionEnabled>". If the disc does not have BEE, the xml will contain "<BusEncryptionEnabled>0</BusEncryptionEnabled>".

	~~To summarize when it comes~~ to ~~dumping purposes; almost all BD-ROM drives have BEE enabled. If the disc you're trying to dump has BEE, and~~ your drive ~~also~~ has BEE, any dumps of that disc will be bad, and any AACSkeys dumped might* be bad as well. You will need to disable BEE before dumping in order to produce a good, working dump of a BEE disc, and to be able to submit your dump to redump.		== Checking to see if your drive has BEE ==

	There are various ways to check if your drive has BEE, but the easiest, given ~~this~~ guide already recommends installing FindVUK, is just to run FindVUK - ShowDriveDetailsForAllDrives.bat and check what it outputs for the drive you're trying to use. Example output of a drive ''with'' BEE:		There are various ways to check if your drive has BEE, but the easiest, given the [[BD-Video Key Extraction]] guide already recommends installing FindVUK, is just to run FindVUK - ShowDriveDetailsForAllDrives.bat and check what it outputs for the drive you're trying to use. Example output of a drive ''with'' BEE:

	<pre>		<pre>
Line 105:		Line 109:
	As seen here, "BusEncryptionSupport : 1" indicates your drive has BEE.		As seen here, "BusEncryptionSupport : 1" indicates your drive has BEE.

	Disabling BEE on your drive is achieved one of three ways:		== Disabling BEE on your drive ==

			Disabling BEE on your drive is achieved in one of three ways:

	'''1. Dump with a drive old enough that the firmware doesn't have BEE in the first place.'''		'''1. Dump with a drive old enough that the firmware doesn't have BEE in the first place.'''
Line 111:		Line 117:
	- I do not know the exact date drives started being produced with BEE, but it may have been around 2011. Regardless, just check whether your drive has BEE via the above method to be sure.		- I do not know the exact date drives started being produced with BEE, but it may have been around 2011. Regardless, just check whether your drive has BEE via the above method to be sure.

	'''2. Dump with a libredrive compatible drive, like ribshark's modified ASUS firmware, after having opened MakeMKV once with that drive, and said drive not having been unpowered long enough to clear its memory. While BEE is still enabled in ribshark's firmware, the libredrive microcode stuff isn't patched out, and so as long as you open makemkv, it'll (among other things) disable the drive's BEE.'''		'''2. Dump with a libredrive compatible drive, like one with ribshark's modified ASUS firmware, after having opened MakeMKV once with that drive, and said drive not having been unpowered long enough to clear its memory. While BEE is still enabled in ribshark's firmware, the libredrive microcode stuff isn't patched out, and so as long as you open makemkv, it'll (among other things) disable the drive's BEE.'''

	- FindVUK will still tell you that your drive has BEE, but will still give you proper AACSkeys dumps as long as you've disabled BEE via makeMKV before running it. ~~DiC~~/redumper/etc will also still give you good dumps as long as you've disabled BEE via makeMKV before running them. If you want to be sure, it's always good to test BEE dumps via VLC, as described below.		- FindVUK will still tell you that your drive has BEE, but will still give you proper AACSkeys dumps as long as you've disabled BEE via makeMKV before running it. DIC/redumper/etc will also still give you good dumps as long as you've disabled BEE via makeMKV before running them. If you want to be sure, it's always good to test BEE dumps via VLC, as described below.

	In order to ensure your dump is good, it's recommended to set up VLC to play back AACS-encrypted ~~bluray~~ .iso files directly, via the necessary steps involving libaacs. If you don't mind the lack of BD-J menus, you might want to disable them in VLC, as it can be difficult to configure Java properly for BD-J, and it'll make it harder to tell if your dump is good if you're trying to figure out if a disc isn't playing because of AACS issues or because of Java issues. If you have set that up already, you can just try playing your dumped .iso in VLC, provided the AACS keys are in your aacs KEYDB.cfg. If they aren't there, but you've dumped your AACS keys via FindVUK already, you can copy the relevant line from FindVUK's VUKbackup cfg file into your KEYDB.cfg. If the disc plays in VLC, you've dumped your disc image and AACSkeys properly. If the disc does not play in VLC, and instead it throws aacs errors in the logs, assuming you've set up VLC to play back AACS-encrypted bluray .iso files properly (test with a non-BEE bluray first to make sure), then you've dumped your disc image or AACSkeys improperly.		In order to ensure your dump is good, it's recommended to set up VLC to play back AACS-encrypted Blu-ray .iso files directly, via the necessary steps involving libaacs. If you don't mind the lack of BD-J menus, you might want to disable them in VLC, as it can be difficult to configure Java properly for BD-J, and it'll make it harder to tell if your dump is good if you're trying to figure out if a disc isn't playing because of AACS issues or because of Java issues. If you have set that up already, you can just try playing your dumped .iso in VLC, provided the AACS keys are in your aacs KEYDB.cfg. If they aren't there, but you've dumped your AACS keys via FindVUK already, you can copy the relevant line from FindVUK's VUKbackup cfg file into your KEYDB.cfg. If the disc plays in VLC, you've dumped your disc image and AACSkeys properly. If the disc does not play in VLC, and instead it throws aacs errors in the logs, assuming you've set up VLC to play back AACS-encrypted bluray .iso files properly (test with a non-BEE bluray first to make sure), then you've dumped your disc image or AACSkeys improperly.

			== Summary ==

			To summarize when it comes to dumping purposes; almost all BD-ROM drives have BEE enabled. If the disc you're trying to dump has BEE, and your drive also has BEE, any dumps of that disc will be bad, and any AACSkeys dumped might* be bad as well. You will need to disable BEE before dumping in order to produce a good, working dump of a BEE disc, and to be able to submit your dump to redump.

	- *I was able to get bad AACSkeys dumps when first discovering this, but I have not been able to reproduce that since. To be safe, though, just re-dump your AACSkeys after disabling BEE via any of the options described.		- *I was able to get bad AACSkeys dumps when first discovering this, but I have not been able to reproduce that since. To be safe, though, just re-dump your AACSkeys after disabling BEE via any of the options described.

	[[Category:Copy Protection Guides\| ]]		[[Category:Copy Protection Guides\| ]]

>NovaAurora at 22:26, 23 January 2025

2025-01-23T22:26:11Z

← Older revision		Revision as of 22:26, 23 January 2025
Line 1:		Line 1:
			A relative minority of BD-Video discs have Bus Encryption Enabled, or BEE. You're relatively unlikely to encounter this on BD-Video discs that are redump-eligible, as BEE was mostly used for more traditional movie releases. However, some redump-eligible discs do stll have it; additionally, all UHD discs have BEE, so if any are made that can be submitted to redump, BEE will have to be dealt with as well.

			There are various ways to check if your disc has BEE, but the easiest, given this guide already recommends installing FindVUK, is just to run FindVUK - AACSkeys.bat and check what it outputs for the disc you're trying to dump. Example relevant section output of a disc ''with'' BEE, on a drive that has BEE:

			<pre>
			-------------------------------------------------------------------------------
			14:59:05 - Get basic AACS data
			-------------------------------------------------------------------------------
			14:59:05 - AACS folder on disc is reachable - ValidateVUK is possible
			14:59:06 - Different VolumeName detected - most likely the disc has been changed... take the new name
			14:59:06 - VolumeName >FIRST_COW<
			14:59:06 - DiscId >EBEF96426CBB4122E4EAC145FCF343B4043352BB< (2020-04-13)
			14:59:06 - DiscType >BD<
			14:59:06 - MKB Revision >70<
			14:59:06 - Disc-BusEncEnabled >1<
			14:59:06 - Drve-BusEncCapable >1<
			14:59:06 - ==> Bus Encryption active!
			14:59:06 - UnitKeyCount >1<
			14:59:06 - >>> UnitKeyENC (1) >4B3CFB16D66D3A73CEDC58D3CBC0E493<
			14:59:06 - UnitKeyCount >1<
			14:59:06 - >>> UnitKeyDEC (1) >3E9945C8BB657E28AE3F282CB7EB163E<
			-------------------------------------------------------------------------------
			14:59:06 - --- PART 2 --- VALIDATE VUK/UNITKEYS ---
			-------------------------------------------------------------------------------
			14:59:06 - Drive is detected as 'REAL BLURAY' drive

			-------------------------------------------------------------------------------
			14:59:06 - Can not validate UnitKeys because of BusEncryption (missing ReadDataKey)!!
			-------------------------------------------------------------------------------
			</pre>

			"Disc-BusEncEnabled >1<" means that your disc has BEE; as seen here, there are various other indications.

			If you're not sure if a disc you submitted in the past has BEE, you can also check the .xml generated by FindVUK to see if it has BEE. If the disc does have BE, the xml will contain "<BusEncryptionEnabled>1</BusEncryptionEnabled>". If the disc does not have BEE, the xml will contain "<BusEncryptionEnabled>0</BusEncryptionEnabled>"

			To summarize when it comes to dumping purposes; almost all BD-ROM drives have BEE enabled. If the disc you're trying to dump has BEE, and your drive also has BEE, any dumps of that disc will be bad, and any AACSkeys dumped might* be bad as well. You will need to disable BEE before dumping in order to produce a good, working dump of a BEE disc, and to be able to submit your dump to redump.

			There are various ways to check if your drive has BEE, but the easiest, given this guide already recommends installing FindVUK, is just to run FindVUK - ShowDriveDetailsForAllDrives.bat and check what it outputs for the drive you're trying to use. Example output of a drive ''with'' BEE:

			<pre>
			################################################################################
			######################
			14:56:05 - ShowDriveDetails for Drive >J:\<
			################################################################################
			######################
			14:56:05 - Vendor >ASUS < ProductId >BW-16D1HT < ProductRevision >3.10<
			ScsiDeviceType >CD/DVD-ROM device< ConnectedTo >USB< Bus

			--COMMON------------------------------------------------------------------------
			--------
			14:56:05 - Drive Vendor : ASUS
			14:56:05 - Drive Model : BW-16D1HT
			14:56:05 - Drive Revision : 3.10
			14:56:05 - Drive VendorSpec : WM01601SIK93G6MA230
			14:56:05 - FirmwareCreationDate : 211901041014
			14:56:05 - Drive Interface : Serial ATAPI
			14:56:05 - Drive Type : BLURAY/DVD/CD-WRITER
			14:56:05 - LoadingMechanism : Tray

			--DRIVE FEATURES----------------------------------------------------------------
			--------
			14:56:05 - Drive Features :
			14:56:05 - Profile List, Core, Morphing, Removeable Medium, Write Protect, R
			andom Readable,
			14:56:05 - Multi-Read, CD Read, DVD Read, Random Writeable, Incremental Stre
			aming Writeable,
			14:56:05 - Formattable, Hardware Defect Management, Restricted Overwrite, CD
			-RW CAV Write,
			14:56:05 - DVD+RW, DVD+R, Rigid Restricted Overwrite, CD Track at Once, CD M
			astering,
			14:56:05 - DVD-R/-RW Write, Layer Jump Recording, CD-RW Media Write Support,
			BD-R POW,
			14:56:05 - DVD+R Dual Layer, BD Read Feature, BD Write Feature, Hybrid Disc,
			Power Management,
			14:56:05 - SMART, CD Audio External Play, Microcode Update, Timeout, DVD-CSS
			, Real Time Streaming,
			14:56:05 - Drive Serial Number, Media Serial Number, DCBs, DVD CPRM, Firmwar
			e Information,
			14:56:05 - AACS

			--DRIVE PROFILES----------------------------------------------------------------
			--------
			14:56:05 - Drive Profiles :
			14:56:05 - BD-RE, BD-R RRM, BD-R SRM, BD-ROM, DVD+R Dual Layer, DVD+R, DVD+R
			W, DVD-R Dual Layer Jump Recording,
			14:56:05 - DVD-R Dual Layer Sequential Recording, DVD-RW Sequential Recordin
			g, DVD-RW Restricted Overwrite,
			14:56:05 - DVD-RAM, DVD-R Sequential Recording, DVD-ROM, CD-RW, CD-R, CD-ROM
			, Removeable disk

			--AACS--------------------------------------------------------------------------
			--------
			14:56:05 - FeatureDescriptor : 01 0D 08 04 1F 01 02 01
			14:56:05 - AacsVersion : 1
			14:56:05 - AacsActive : 0
			14:56:05 - BindingNonceGenSupp : 1
			14:56:05 - BindingNonceBlockCnt : 1
			14:56:05 - BusEncryptionSupport : 1
			14:56:05 - ReadDriveCertificate : 1
			14:56:05 - AgidCount : 2
			14:56:05 - Drive is detected as 'REAL BLURAY' drive
			14:56:05 - Drive is already in the KnownDrivesList
			</pre>

			As seen here, "BusEncryptionSupport : 1" indicates your drive has BEE.

			Disabling BEE on your drive is achieved one of three ways:

			'''1. Dump with a drive old enough that the firmware doesn't have BEE in the first place.'''

			- I do not know the exact date drives started being produced with BEE, but it may have been around 2011. Regardless, just check whether your drive has BEE via the above method to be sure.

			'''2. Dump with a libredrive compatible drive, like ribshark's modified ASUS firmware, after having opened MakeMKV once with that drive, and said drive not having been unpowered long enough to clear its memory. While BEE is still enabled in ribshark's firmware, the libredrive microcode stuff isn't patched out, and so as long as you open makemkv, it'll (among other things) disable the drive's BEE.'''

			- FindVUK will still tell you that your drive has BEE, but will still give you proper AACSkeys dumps as long as you've disabled BEE via makeMKV before running it. DiC/redumper/etc will also still give you good dumps as long as you've disabled BEE via makeMKV before running them. If you want to be sure, it's always good to test BEE dumps via VLC, as described below.

			In order to ensure your dump is good, it's recommended to set up VLC to play back AACS-encrypted bluray .iso files directly, via the necessary steps involving libaacs. If you don't mind the lack of BD-J menus, you might want to disable them in VLC, as it can be difficult to configure Java properly for BD-J, and it'll make it harder to tell if your dump is good if you're trying to figure out if a disc isn't playing because of AACS issues or because of Java issues. If you have set that up already, you can just try playing your dumped .iso in VLC, provided the AACS keys are in your aacs KEYDB.cfg. If they aren't there, but you've dumped your AACS keys via FindVUK already, you can copy the relevant line from FindVUK's VUKbackup cfg file into your KEYDB.cfg. If the disc plays in VLC, you've dumped your disc image and AACSkeys properly. If the disc does not play in VLC, and instead it throws aacs errors in the logs, assuming you've set up VLC to play back AACS-encrypted bluray .iso files properly (test with a non-BEE bluray first to make sure), then you've dumped your disc image or AACSkeys improperly.

			- *I was able to get bad AACSkeys dumps when first discovering this, but I have not been able to reproduce that since. To be safe, though, just re-dump your AACSkeys after disabling BEE via any of the options described.

	[[Category:Copy Protection Guides\| ]]		[[Category:Copy Protection Guides\| ]]

>NovaAurora: Created page with " "

2025-01-23T20:18:08Z

Created page with " "

New page

[[Category:Copy Protection Guides| ]]