Disable SECURE BIOS when install Windows 8 , if not Windows 8 cannot boot up !
Disable SECURE BIOS when install Windows 8 , if not Windows 8 cannot boot up !
Source : Internet
China plays the psychological game while the Americans prepare for another war with Iran
This is a high resolution photo China just published of a satellite imagery of every F-22 Raptor at Israel’s Ovda Air Base with each aircraft tagged in Chinese characters on Weibo
AND this is another high resolution Chinese satellite photo of American warships at their base in Bahrain with additional photos showing every American warships entering and leaving that naval base:
The same week, China announced that it had sold Iran CM-302 supersonic anti-ship missiles.
This is what China is upto:
Beijing is running a strategic psycho-opt stress test in real time - arm the adversary, map its force disposition, publish it to degrade its capability.
THAN sit back and watch whether Washington depletes its weaponries and manpower against a regional power
while China sit back and watch
Windows 10 Operating System _ error message " Recovery .......Your PC/Device needs to be repaired .......The Boot Configuration Data file is missing some required information ....... File: \Boot\BCD ....... Error code: 0xc0000034 .......You'll need to use recovery tools. If you don't have any installation media (like a disc or USB device), contact your PC administrator or PC/Device manufacturer "
MICROSOFT Copilot Answer
That error means your Boot Configuration Data (BCD) is corrupted or missing, which prevents Windows from starting. The good news: you can usually fix it without losing your files. Here’s a clear step‑by‑step guide:
In Command Prompt, type these commands one by one (press Enter after each):
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
Would you like me to also walk you through how to create the Windows installation USB step by step, in case you don’t already have one?
Hi Copilot, i have a Laptop with Windows 10 Operating System installed inside it. When I switched on my Laptop , I want my Laptop automatically go straight to a particular web site or a specific website that I have in mind. But the problem is, Windows 10 Operating system imposed so much security measure inside my Laptop , so much so that I have to key in my PIN NUMBER , i have to key in my password , etc., etc. And now , all of a sudden if i shutdown my Laptop quite often in a matter of short time , MICROSOFT impose another security measure by saying that I have to wait another 2 hours before I can login into my Laptop. I am not working for the PENTAGON , and I believe the millions of consumers who use the Windows 10 Operating System on their machines are also not working for the PENTAGON , too. I believe the millions of consumers who use the Windows 10 OS in their machines have the right to use their machines the way he or she pleases. I have been using Windows Operating System for so many years now but when the Windows 10 OS in my Laptop says I have to wait for another 2 hours to try and login again , this really frustrates me. Has it ever occured to MICROSOFT that sometimes the people who work with Windows 10 machines are Computer Technicians , IT Technicians and Windows 10 Hobbyist who repair and trouble-shoot and play around and dabble around with Windows 10 Laptop or Windows 10 PC/Desktop or Windows 10 Tablet or Windows 10 Engineering Workstation , where all these people sometimes have to switch on and off their machines very often , so much so that , THERE ARE REPEATED SHUTDOWNS , for the sake to get the customer machines up and running , as quickly as possible. Copilot , if 2 hours is the waiting time to get login into the customers Windows 10 machines , how can these Computer Technicians or IT Technicians able to do their job in a productive manner ??? Copilot , in my opinion , MICROSOFT , have to rethink about this issue or problem. Copilot , could you share your thoughts and ideas regarding this problem. THANKS.
MICROSOFT Copilot Answer
You’ve raised a very real frustration that many Windows 10 users and technicians share. Let me break down the situation and offer some perspective:
PINs and passwords: These are standard security layers to protect against unauthorized access. Microsoft designed them with the assumption that most laptops are personal devices containing sensitive data.
Lockout periods (like the 2‑hour wait): This is part of account protection. If Windows detects repeated failed logins or frequent shutdown/restart cycles, it may trigger a temporary lockout to prevent brute‑force attacks. From a security standpoint, this makes sense—but from a technician’s standpoint, it’s disruptive.
For everyday users: Microsoft prioritizes protecting data over convenience. That’s why it feels like “Pentagon‑level” security even for home users.
For technicians and hobbyists: The system doesn’t distinguish between someone troubleshooting hardware/software and someone maliciously trying to break in. That’s where the friction lies.
Local accounts: Using a local account instead of a Microsoft account can reduce some of these restrictions (though you lose cloud sync features).
Group Policy / Registry tweaks: In professional or lab environments, administrators often adjust policies to disable lockout timers or reduce password complexity. This isn’t exposed in consumer settings, but IT pros can configure it.
Virtual machines or test rigs: Many technicians use VMs or secondary devices to avoid constant lockouts on their main machine.
Feedback to Microsoft: The frustration you describe is valid. Microsoft does collect user feedback through the Feedback Hub app in Windows 10. If enough technicians highlight this issue, it could influence future updates.
You’re absolutely right: technicians, engineers, and hobbyists need flexibility. A blanket 2‑hour lockout undermines productivity in repair and troubleshooting scenarios. Microsoft’s approach is heavily tilted toward protecting the average consumer, but it doesn’t account for advanced users who deliberately restart machines repeatedly. Ideally, there should be a toggle or “technician mode” that allows professionals to bypass these restrictions when needed.
If you were to draft feedback to Microsoft, I’d suggest framing it around:
The productivity impact for IT professionals.
The need for an optional setting (not removing security entirely, but giving advanced users control).
The fact that security should be balanced with usability, especially in non‑sensitive environments.
Would you like me to help you draft a clear, professional feedback message to Microsoft that captures your frustration and proposes a solution? That way, your voice could be part of the collective push for change.You’ve raised a very real frustration that many Windows 10 users and technicians share. Let me break down the situation and offer some perspective:
PINs and passwords: These are standard security layers to protect against unauthorized access. Microsoft designed them with the assumption that most laptops are personal devices containing sensitive data.
Lockout periods (like the 2‑hour wait): This is part of account protection. If Windows detects repeated failed logins or frequent shutdown/restart cycles, it may trigger a temporary lockout to prevent brute‑force attacks. From a security standpoint, this makes sense—but from a technician’s standpoint, it’s disruptive.
For everyday users: Microsoft prioritizes protecting data over convenience. That’s why it feels like “Pentagon‑level” security even for home users.
For technicians and hobbyists: The system doesn’t distinguish between someone troubleshooting hardware/software and someone maliciously trying to break in. That’s where the friction lies.
Local accounts: Using a local account instead of a Microsoft account can reduce some of these restrictions (though you lose cloud sync features).
Group Policy / Registry tweaks: In professional or lab environments, administrators often adjust policies to disable lockout timers or reduce password complexity. This isn’t exposed in consumer settings, but IT pros can configure it.
Virtual machines or test rigs: Many technicians use VMs or secondary devices to avoid constant lockouts on their main machine.
Feedback to Microsoft: The frustration you describe is valid. Microsoft does collect user feedback through the Feedback Hub app in Windows 10. If enough technicians highlight this issue, it could influence future updates.
You’re absolutely right: technicians, engineers, and hobbyists need flexibility. A blanket 2‑hour lockout undermines productivity in repair and troubleshooting scenarios. Microsoft’s approach is heavily tilted toward protecting the average consumer, but it doesn’t account for advanced users who deliberately restart machines repeatedly. Ideally, there should be a toggle or “technician mode” that allows professionals to bypass these restrictions when needed.
If you were to draft feedback to Microsoft, I’d suggest framing it around:
The productivity impact for IT professionals.
The need for an optional setting (not removing security entirely, but giving advanced users control).
The fact that security should be balanced with usability, especially in non‑sensitive environments.
Would you like me to help you draft a clear, professional feedback message to Microsoft that captures your frustration and proposes a solution? That way, your voice could be part of the collective push for change.
Got it — let’s walk through the troubleshooting step by step so you can get your Bluetooth headset connected to Fedora Workstation 43:
lsusb | grep -i bluetooth
This confirms Fedora sees your dongle.rfkill list
Make sure Bluetooth isn’t blocked.sudo dnf install bluez bluez-tools
sudo systemctl start bluetooth
sudo systemctl enable bluetooth
bluetoothctl
scan on
XX:XX:XX:XX:XX:XX).pair XX:XX:XX:XX:XX:XX
connect XX:XX:XX:XX:XX:XX
trust XX:XX:XX:XX:XX:XX
sudo dnf install pavucontrol
bluetoothctl.👉 Quick test: After following these steps, try running bluetoothctl and see if your headset shows up during scan on. If it doesn’t, the issue is likely with the dongle itself.
Do you want me to guide you through checking whether your dongle is fully supported by Fedora, or focus on the headset pairing side?