This is my current PC:
SSD: 2 TB NVME, Windows 11 Pro installed;
second drive 4 TB regular SSD
Both encrypted with BitLocker, which uses TPM and PIN. CPU is i5 11400, MSI Z590-A Pro. The motherboard uses latest firmware, so are all apps and Windows.
Windows using a password, too, after I enter BitLocker's. Both SSDs encrypted. 32 GB of RAM (DDR-4).
Using: USB-C to Micro-B 3.2, external Blu-ray drive. Had to buy a 2 meter-cable.
Video card: RTX DUAL-RTX3060-O12G-V2
Monitor: 4K, Acer, XV280K-B
+++++++++++++++++++++
Also, I discovered the following:
- The monitor had to be changed: AUTO SOURCE set to OFF, and INPUT: choose HDMI 1 (2.0). Otherwise, it would show no screen after installing this Windows. I even had to connect the PC to a TV, to configure later, before I figured out this, during a format.
- BitLocker also had to use a particular CMD/Windows 11 setting, otherwise the monitor would be turned off during a restart or I turn it ON for the 1st time, and without this change, the CPU would also power off:
bcdedit /set {bootmgr} bootshutdowndisabled 1
+++++++++++++
EXPLANATION required before I tell what's wrong:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The command bcdedit /set {bootmgr} bootshutdowndisabled 1 affects the behavior of the system during the shutdown process and its interaction with BitLocker pre-boot authentication in the following way:
Preventing Clean Shutdown: By setting bootshutdowndisabled to 1, the system is configured to avoid performing a clean shutdown when shutting down the computer. Instead, it forces a "dirty" shutdown, which means the system does not fully power off but instead enters a hibernation-like state.
Impact on BitLocker and Monitor: When BitLocker is enabled with pre-boot authentication (requiring a PIN or password before the operating system loads), the system typically shuts down completely after the user enters the correct PIN. However, with bootshutdowndisabled set to 1, the system skips the normal shutdown process and enters the hibernation-like state instead.
Maintaining Power for BitLocker: By avoiding a clean shutdown, the system maintains power to essential components, including the CPU and memory, during the boot process. This ensures that BitLocker's pre-boot authentication process remains active, allowing the user to enter the PIN or password to unlock the encrypted drive.
Impact on Monitor: In some configurations, when the system enters this hibernation-like state, it may result in the monitor turning off or entering a low-power state. However, the behavior can vary depending on the specific hardware, firmware settings, and power management configurations of the system.
User Interaction: When the user restarts the computer or turns it on after it enters this hibernation-like state, the monitor may remain off until the user interacts with the system (e.g., by pressing a key or entering the BitLocker PIN). Once the user provides input, the monitor typically turns on, and the BitLocker pre-boot authentication screen is displayed, prompting the user to enter the PIN.
Overall, enabling bootshutdowndisabled with BitLocker helps ensure that the system maintains power and remains in a state where pre-boot authentication can occur, allowing users to unlock encrypted drives without the need for a clean shutdown and reboot process. However, the exact behavior of the monitor during this process can vary depending on system configuration and settings.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
What is happening and I can't figure out WHY:
- I bought 100 BD-Rs from RITEK, and only the last 5 (at least) turned out to be coasters. All of them. I tried with ImgBurn, CDBurnerXP, even BurnAware, all these apps returned some sort of error, stuck with Writing LEAD IN, or Write Error after a while, or rejecting after a few minutes the media. One of them returned a Writing error after almost 90%.
It seems:
- Either these last discs are broken (perhaps some sort of surface scratch or smudge (and I did notice a very small in a few of them), even if minimal, can spoil the burning), or my drive, after more than 200 burnings, started to fail.
I still need to verify which of these scenarios happened. And in all attempts of these last that failed, I used the slowest speeds.
But here's the thing:
- Once the burning failed, ImgBurn or the app was not responding, and I either had to hit control+Alt+DEL and force their closure, or restart the machine. Because Windows was pratically stuck with this process, in terms of hanging the app opened in Explorer, so it took a while to restart (you know, when a program is taking longer to be cleared of memory/task process), or I simply stopped waiting after the "Windows is restarting" screen, and hit the power button of my PC case.
What happened AFTER (and this more than once, so it's not a coincidence, it's a certainty) was what surprised me the most:
- After Windows restarted, or I turned the entire PC off (after a failed BD-R burning), the monitor would go off completely - when it's on, we get a blue LED - when it's off, an orange.
The LED remained orange, so it said "no signal", and the PC wasn't turned off. It was ON. And how did I find it was on the BitLocker PIN screen? I typed, despite no image on this ACER LCD - my password - and voila! The monitor turned ON again, and went to the actual Windows login screen.
And to make sure the
bcdedit /set {bootmgr} bootshutdowndisabled 1
Was active, I asked IA how to verify that. And it is enabled. Which explains why the PC doesn't turn off by itself, if I don't inform BitLocker's PIN.
This is a bug that is very, very odd, indeed.
It looks like the ASUS external Blu-ray drive, when dealing with this MSI motherboard (or perhaps the RTX 3060 card), somehow causes the monitor to go off after a restart, if the burning fails.
But why? There's no reason why this would ever happen. If I didn't know better, I would have to plug a TV again in this computer, just to see any image again.
And once I am logged into Windows, everything is fine, again, for good. Even after I turn off the PC completely.
SSD: 2 TB NVME, Windows 11 Pro installed;
second drive 4 TB regular SSD
Both encrypted with BitLocker, which uses TPM and PIN. CPU is i5 11400, MSI Z590-A Pro. The motherboard uses latest firmware, so are all apps and Windows.
Windows using a password, too, after I enter BitLocker's. Both SSDs encrypted. 32 GB of RAM (DDR-4).
Using: USB-C to Micro-B 3.2, external Blu-ray drive. Had to buy a 2 meter-cable.
Video card: RTX DUAL-RTX3060-O12G-V2
Monitor: 4K, Acer, XV280K-B
+++++++++++++++++++++
Also, I discovered the following:
- The monitor had to be changed: AUTO SOURCE set to OFF, and INPUT: choose HDMI 1 (2.0). Otherwise, it would show no screen after installing this Windows. I even had to connect the PC to a TV, to configure later, before I figured out this, during a format.
- BitLocker also had to use a particular CMD/Windows 11 setting, otherwise the monitor would be turned off during a restart or I turn it ON for the 1st time, and without this change, the CPU would also power off:
bcdedit /set {bootmgr} bootshutdowndisabled 1
+++++++++++++
EXPLANATION required before I tell what's wrong:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The command bcdedit /set {bootmgr} bootshutdowndisabled 1 affects the behavior of the system during the shutdown process and its interaction with BitLocker pre-boot authentication in the following way:
Preventing Clean Shutdown: By setting bootshutdowndisabled to 1, the system is configured to avoid performing a clean shutdown when shutting down the computer. Instead, it forces a "dirty" shutdown, which means the system does not fully power off but instead enters a hibernation-like state.
Impact on BitLocker and Monitor: When BitLocker is enabled with pre-boot authentication (requiring a PIN or password before the operating system loads), the system typically shuts down completely after the user enters the correct PIN. However, with bootshutdowndisabled set to 1, the system skips the normal shutdown process and enters the hibernation-like state instead.
Maintaining Power for BitLocker: By avoiding a clean shutdown, the system maintains power to essential components, including the CPU and memory, during the boot process. This ensures that BitLocker's pre-boot authentication process remains active, allowing the user to enter the PIN or password to unlock the encrypted drive.
Impact on Monitor: In some configurations, when the system enters this hibernation-like state, it may result in the monitor turning off or entering a low-power state. However, the behavior can vary depending on the specific hardware, firmware settings, and power management configurations of the system.
User Interaction: When the user restarts the computer or turns it on after it enters this hibernation-like state, the monitor may remain off until the user interacts with the system (e.g., by pressing a key or entering the BitLocker PIN). Once the user provides input, the monitor typically turns on, and the BitLocker pre-boot authentication screen is displayed, prompting the user to enter the PIN.
Overall, enabling bootshutdowndisabled with BitLocker helps ensure that the system maintains power and remains in a state where pre-boot authentication can occur, allowing users to unlock encrypted drives without the need for a clean shutdown and reboot process. However, the exact behavior of the monitor during this process can vary depending on system configuration and settings.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
What is happening and I can't figure out WHY:
- I bought 100 BD-Rs from RITEK, and only the last 5 (at least) turned out to be coasters. All of them. I tried with ImgBurn, CDBurnerXP, even BurnAware, all these apps returned some sort of error, stuck with Writing LEAD IN, or Write Error after a while, or rejecting after a few minutes the media. One of them returned a Writing error after almost 90%.
It seems:
- Either these last discs are broken (perhaps some sort of surface scratch or smudge (and I did notice a very small in a few of them), even if minimal, can spoil the burning), or my drive, after more than 200 burnings, started to fail.
I still need to verify which of these scenarios happened. And in all attempts of these last that failed, I used the slowest speeds.
But here's the thing:
- Once the burning failed, ImgBurn or the app was not responding, and I either had to hit control+Alt+DEL and force their closure, or restart the machine. Because Windows was pratically stuck with this process, in terms of hanging the app opened in Explorer, so it took a while to restart (you know, when a program is taking longer to be cleared of memory/task process), or I simply stopped waiting after the "Windows is restarting" screen, and hit the power button of my PC case.
What happened AFTER (and this more than once, so it's not a coincidence, it's a certainty) was what surprised me the most:
- After Windows restarted, or I turned the entire PC off (after a failed BD-R burning), the monitor would go off completely - when it's on, we get a blue LED - when it's off, an orange.
The LED remained orange, so it said "no signal", and the PC wasn't turned off. It was ON. And how did I find it was on the BitLocker PIN screen? I typed, despite no image on this ACER LCD - my password - and voila! The monitor turned ON again, and went to the actual Windows login screen.
And to make sure the
bcdedit /set {bootmgr} bootshutdowndisabled 1
Was active, I asked IA how to verify that. And it is enabled. Which explains why the PC doesn't turn off by itself, if I don't inform BitLocker's PIN.
This is a bug that is very, very odd, indeed.
It looks like the ASUS external Blu-ray drive, when dealing with this MSI motherboard (or perhaps the RTX 3060 card), somehow causes the monitor to go off after a restart, if the burning fails.
But why? There's no reason why this would ever happen. If I didn't know better, I would have to plug a TV again in this computer, just to see any image again.
And once I am logged into Windows, everything is fine, again, for good. Even after I turn off the PC completely.
Last edited: