Recommended Posts

  On 06/04/2025 at 09:53, Nick H. said:

https://en.wikipedia.org/wiki/Bootloader

Also see this: 

GRUB allows me to dual-boot. Windows' BOOTMGR does not as far as I'm aware.

Expand  

Windows bootmanager has allowed dual booting for years, it's not at straightforward to setup as Grub but I used to dual boot Windows and Linux that way even back in the early 2000s

https://www.windowscentral.com/software-apps/windows-11/how-to-create-a-dual-boot-setup-on-windows-11 step by step instructions if you're interested.

GRUB is the piece of code that sits between the BIOS completing its power on self test and the startup and initialisation process of the operating system. It's the code that finds the operating system(s) on the disk and performs the handover. They can do this because they understand where the code is that needs to be executed and have the file system drivers necessary to read it (which the BIOS doesn't). They also allow multiple operating systems to exist concurrently on the device. Under Windows the GRUB equivalent was DOS, then NTLDR and finally BootMGR on current releases.

It used to be common that Linux would boot using LILO and not GRUB, but GRUB is newer, better featured and better maintained, so most dists use GRUB.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • AS data is written to 1 disk its also written to the other disk in the raid pool. RAID - Wikipedia
    • Its still there, but annoyingly you have to left click the word now and not right click as many millions of peoples muscle memory are quickly finding out.
    • Their initial offerings (AV) were fine, but then there was just absolute stagnation and they had no idea what to do with themselves so they created solutions to problems that really didn't exist, convinced users they did but then realised nobody was buying into it, so bundled their bloated crap with OEM builds. Arguably, the whole AV market got a bad name with end consumers for a period because of companies such as Norton.
    • Windows Server 2025 security baseline to get more frequent updates, streamlines settings by Paul Hill Microsoft has announced the release of the June 2025 revision of its security baseline package for Windows Server 2025 (v2506), it is now available to download from the Microsoft Security Compliance Toolkit. After downloading it, you can test the recommended configurations in your environment and customize or implement them as you see fit. To deal with the evolving threat landscape, new Windows features, and community feedback, Microsoft is planning to revise the Windows Server baseline more frequently in the future. Windows Server security baselines are a collection of Microsoft-recommended configuration settings that help administrators establish secure and consistent Windows Server environments. This is the first security baseline update for Windows Server 2025 since January, a summary of the changes is presented in this table: Security Policy Change Summary Deny log on through Remote Desktop Services Allow remote logon for non-admin local accounts on MS and add “BUILTIN\Guests” to both DC and MS. WDigest Authentication Remove from the baseline Allow Windows Ink Workspace Remove from the baseline Audit Authorization Policy Change Set to “Success” in both DC and MS Include command line in process creation events Enable in both DC and MS Control whether exclusions are visible to local users Moved to Not Configured as it is overridden by the parent setting. Of these changes, the removal of WDigest Authentication and the addition of Include command line in process creation events are significant. Microsoft said it removed WDigest Authentication from the security baseline because it is no longer necessary for Windows Server 2025. The policy was originally enforced so that WDigest couldn’t store plaintext passwords in memory, which was a significant theft risk. Since the 24H2 update in Windows Server 2022, the policy has been deprecated, so there’s no need to enforce this setting. The update also adds Include command line in process creation events to improve the visibility of how processes are executed across the system. By capturing the command-line arguments, it makes it easier to detect and investigate malicious activity that may otherwise seem legitimate. If you want to learn more about the other changes in a bit more depth, refer to Microsoft’s announcement of this security baseline update.
  • Recent Achievements

    • One Month Later
      Leonard grant earned a badge
      One Month Later
    • Week One Done
      pcdoctorsnet earned a badge
      Week One Done
    • Rising Star
      Phillip0web went up a rank
      Rising Star
    • One Month Later
      Epaminombas earned a badge
      One Month Later
    • One Year In
      Bert Fershner earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      537
    2. 2
      ATLien_0
      205
    3. 3
      +FloatingFatMan
      167
    4. 4
      Michael Scrip
      151
    5. 5
      Som
      127
  • Tell a friend

    Love Neowin? Tell a friend!