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

    • The actual download size is ~130–180 MB, not 100 MB.
    • Slight change of pace for me! Gunnar & the Grizzly Boys - Standard American (Official)  
    • draw.io Desktop 30.2.4 by Razvan Serea draw.io desktop is a downloadable security-first diagramming application that runs on Windows, MacOS and Linux. Creating diagrams in the desktop app doesn’t need an internet connection. This is useful when you are disconnected or when you must create diagrams in a highly secure environment, where data protection is of the utmost importance. When you use the draw.io desktop app, your diagrams will be stored on your local device. Because this is a stand-alone application, also designed to run offline, there are no interfaces to cloud storage platforms available. Of course, you can still store your diagrams in folders that are synchronised to your cloud storage if you wish. Easy-to-use diagram editor The draw.io apps work just like the office and drawing tools you are used to using. Drag and drop shapes from the shape libraries and drag to draw connectors between them. Drag connectors to add waypoints and set a precise shape and position, or let them reroute automatically. Double click and start typing to add a label to anything. Create tables and swimlane flows with a familiar tool. Style shapes and connectors with customisable palettes, sketch options, fonts and text formatting tools. Search for shapes, including in open-source icon libraries. Use our vast libraries of shapes and templates, organised into logical categories, to create a range of diagrams and infographics. Generate diagrams from text descriptions using our smart templates. Diagram faster with keyboard shortcuts. draw.io Desktop 30.2.4 changelog: Uses electron 42.4.1 Updates to draw.io core 30.2.4. Download: draw.io 64-bit | Standalone ~100.0 MB (Open Source) Download: draw.io 32-bit | ARM64 | ARM64 Standalone Links: draw.io Home Page | Project page @GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft will soon allow some users to block Copilot from analyzing their Office files by Usama Jawad Microsoft Purview is a pretty useful data governance, security, and management service that allows customers to gain enhanced visibility and control over their content. It's meant for commercial customers, such as organizations that are storing data at scale. As AI continues to expand and infiltrate every corner of a firm, many are a bit conscious about the technology gaining access to their confidential data. Microsoft is now making a configuration change that will allow such customers to rest easy. Right now, users within an organization have the option to apply Purview sensitivity labels (when available) to secure certain files and label them as such. For example, if you apply the "Confidential" label on an Excel file, the file will be encrypted, and a "confidential" watermark will be applied to it. So, if this file is shared with anyone, they are aware that its access is supposed to be restricted. Up until now, Microsoft was allowing some connected experiences, like its AI services, to analyze files, regardless of their sensitivity label. This is of major concern to most organizations, as a recent example highlighted how confidential emails with data loss prevention (DLP) policies like privacy labels were being uploaded to Copilot for analysis. As such, Microsoft is updating an existing Purview data label sensitivity setting that prevents "some connected experiences that analyze content", from being blocked completely from doing this. The label isn't changing, but the blocking is now being enforced across all connected services (including Copilot and other AI tools), and now extends to Microsoft Word, Excel, and PowerPoint. Files with the label applied already will get this enhancement automatically too once it becomes available. Microsoft has urged IT admins to inform their respective helpdesk and compliance teams, update internal documentation, and review sensitivity labels to ensure that they meet their respective compliance needs. This change is tagged as MC1297982 in the Message Center. General availability is scheduled to begin in a phased manner soon and will complete by the end of next month. That said, it is important to note that this only applies to commercial customers who have a license that allows them to use Purview.
    • llamas are unruly going haywire in New Guinea.
  • 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
      589
    2. 2
      +Edouard
      190
    3. 3
      Michael Scrip
      76
    4. 4
      PsYcHoKiLLa
      75
    5. 5
      neufuse
      72
  • Tell a friend

    Love Neowin? Tell a friend!