Recommended Posts

Thought Microsoft Security Essentials when released would cut down on Family infecting there PC's with junk, but I find that i'm still helping family remove Trojans and junk off there PC's pretty regularly, gotten to the point only help Mom these days, rest I recommend to local small PC shop, as too much time cleaning there PCs

Most of Family though removed MSE when they saw it failed certification tests...So I guess up to them now what they use.

Maybe it's time that you educate your family instead of blaming MS for your woes....not that this has ANYTHING to do with the topic..of course.

If you turn off secure boot in the EFI Bios then no you have zero issues dual booting into any other OS. Now, if the OEM locks down the EFI bios that is booty. I build my own rigs so I never have these issues. My latest rig the EFI Bios shipped with secure boot turned on and I scratched my head for a few minutes until I hunted down why I was getting a BCD loader non signed certificate error and then turned off secure boot.

I will have to probe some of my clients white boxes and see if they have the ability to turn off secure boot.

UEFI secure boot is fine as long:

- Its allow Hardware Owner (not the hardware vendor) to change the UEFI keys

- hardware owner are allowed to disable the secure boot.

if the UEFI was set to disallow hardware owner to change the key, yes its became a locked system with planned obsolescene in mind.

its interesting that before announcing to build Surface RT themself,

Microsoft insist that users must be disallowed to disable secure boot, when secure boot is used in ARM system.

but user should be allowed to disable it on x86-64 system.

"On non-ARM systems, it is required to implement the ability to disable Secure Boot ..."

...

"On an ARM system, it is forbidden to enable Custom Mode. ... Disabling Secure MUST NOT be possible on ARM systems," Microsoft states.

why the differences?

UEFI secure boot is fine as long:

- Its allow Hardware Owner (not the hardware vendor) to change the UEFI keys

- hardware owner are allowed to disable the secure boot.

if the UEFI was set to disallow hardware owner to change the key, yes its became a locked system with planned obsolescene in mind.

its interesting that before announcing to build Surface RT themself,

Microsoft insist that users must be disallowed to disable secure boot, when secure boot is used in ARM system.

but user should be allowed to disable it on x86-64 system.

why the differences?

Because on ARM, the OS is tailored to the hardware. It's pointless. Tablets are not tinker toys. Don't want Windows 8? Buy another tablet.

  • Like 2

Because on ARM, the OS is tailored to the hardware. It's pointless. Tablets are not tinker toys. Don't want Windows 8? Buy another tablet.

Sure they are. You just need to look at sites like XDA-Developers for proof of that.

  • Like 1

If it weren't for the fact that 90% of PC users are uneducated and unwilling to learn about what they bought/use (but also cannot live without it these days) we wouldn't need "Secure Boot".

I got fed up of helping people with viruses and trojans taking up hours of my time (mostly for free) that I just prefer they go to someone else or even pay for a professional to help them now.

There is also huge numbers of user who uses "FREE" version and refuse to download update.

I wonder how many manufactures allow you to turn off secure boot and how many don't? I have never seen a list of companies that say.

I bought an ASUS laptop back in December (A45A-MX2-H). It had the ability to disable or turn off UEFI Secure Boot. It has seen three or so UEFI/BIOS updates and since then, the option has been hidden or removed.

Because on ARM, the OS is tailored to the hardware. It's pointless. Tablets are not tinker toys. Don't want Windows 8? Buy another tablet.

by your logic, Surface RT (Tegra3 - ARM based) was not a toy,

but

Surface Pro (x86-64 based) is a toy ?

surely that the opposite of what Microsoft have to say in their marketing campaign ...

Okay, you won't be able to disable it on an ARM system. You can disable it on a x86-64 systems. UEFI secure boot can be viewed as both a good and bad thing. For the majority of people using WIN8 on tablets (end user customers) how many really want to use dual boot anyways?

Most of the people in my family and my friends, simply want to turn on their computers go online, play games or do things without the hassle of viruses and their PC's giving them a hard time. People just want easy to use, reliable computers to do what they want to do.

Most tablet PC owners, or those that own portable devices are not tinkering around with things to these levels. I'm pretty certain there will be open alternatives for those which do. If you don't want to deal with UEFI Win8 lockdowns on a ARM tablet. Don't buy one, Buy another tablet. The Market will be responding to this.

An alternative to dual booting, is running Linux in a Virtual system (VMware and etc), does UEFI prevent this from happening on an ARM system? It would seem that if Linux applications were so important to somebody they would explore alternatives besides dual boot.

Hackers/Virus programmers exploit how open a system really is. If lock downs like this mean, I get less phone calls for help from family and friends. GREAT! They ain't so tech savvy to begin with. They buy a new PC, love it for awhile, and then within a couple of months are calling it piece of junk that they'd love to throw out the damn window. If WIN8 ARM tablets prove to be more stable and reliable because of a lock down like this. This should be a great thing. Less headaches for Tablet makers, Microsoft and those of us with family and friends constantly bugging us to help fix their computer issues.

I don't have people bugging me to come over and fix their xBox, their Sony Play Stations, or their iPADs or iPhones (insert list of devices more stable compared to an X86/64 PC running Windows whatever).

I wonder how many manufactures allow you to turn off secure boot and how many don't? I have never seen a list of companies that say.

It is required for Windows 8 certification. If the PC has a Windows 8 sticker, users should be able to disable it.

This topic is now closed to further replies.
  • Posts

    • Anybody that thinks flying cars were possible are idiots. Everyone would basically need a pilot licence, can you imagine how insane and dangerous that would be, people can barely handle driving on land safely right now.
    • Microsoft Edge 149.0.4022.80 by Razvan Serea Microsoft Edge is a super fast and secure web browser from Microsoft. It works on almost any device, including PCs, iPhones and Androids. It keeps you safe online, protects your privacy, and lets you browse the web quickly. You can even use it on all your devices and keep your browsing history and favorites synced up. Built on the same technology as Chrome, Microsoft Edge has additional built-in features like Startup boost and Sleeping tabs, which boost your browsing experience with world class performance and speed that are optimized to work best with Windows. Microsoft Edge security and privacy features such as Microsoft Defender SmartScreen, Password Monitor, InPrivate search, and Kids Mode help keep you and your loved ones protected and secure online. Microsoft Edge has features to keep both you and your family protected. Enable content filters and access activity reports with your Microsoft Family Safety account and experience a kid-friendly web with Kids Mode. The new Microsoft Edge is now compatible with your favorite extensions, so it’s easy to personalize your browsing experience. Microsoft Edge 149.0.4022.80 changelog: Fixes Fixed an issue that prevented QR code generation from working. Feature updates Intune MAM Protected Downloads. The protected downloads feature for Intune MAM will now save downloaded files to the Documents > Microsoft Edge > Downloads folder in OneDrive. Extensions monitoring in the Edge management service. The Microsoft Edge management service now allows admins to gain visibility into extensions installed across their managed users. From the extensions monitoring page, admins can see which extensions have been installed as well as manage user requests for blocked extensions. For more information, see Microsoft Edge Extensions Monitoring. Validate Edge builds early with enterprise preview. Enterprise preview provides a simpler way for admins to flight pre-release Edge builds to their users. To reduce friction and bolster usage, users will receive pre-release builds directly inside of their Stable Edge application. Admins can allow users to easily opt-out of the preview experience, using built-in rollback to switch between their pre-release and stable channels with ease. Microsoft 365 admin center users can configure the feature, view their flighting population, and receive personalized recommendations all in one place. For more information, see Get started with Enterprise Preview in Microsoft Edge. Download: Microsoft Edge (64-bit) | 193.0 MB (Freeware) Download: Microsoft Edge (32-bit) | 170.0 MB Download: Microsoft Edge (ARM64) | 188.0 MB View: Microsoft Edge Website | Release History Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!