I’m going to comment again, not to be an asshole, but because this is an entirelt separate stream of thoughts from my previous comment:

‘GUI/UX for everything, absolutely no CLI’ approach

That’s not a distro thing, it’s a Desktop Environment thing. I personally use GNOME on my daily driver, but I’ve also used Xfce and MATE and gotten away with those. I’d say that GNOME is probably the most “idiot proof,” which is why I use it, but YMMV.

Linux “requiring the CLI” hasn’t been true for quite a few years now, it just has stuck around for a couple of reasons (imo):

1. Tutorials/guides/advice about Linux tends to focus on the CLI because it’s easier to figure out someone’s OS and have them copy-paste a command, than to find out the specifics of their graphical setup and walk them through every window and button press.

2. New users need to know and understand the difference between Kernel, OS, and Desktop Environment to find the answers they’re looking for.

If you tell Grandma that you installed Linux for her, the first time she tries to figure it out herself, she’s gonna search “how to change volume in Linux” on Google, and she’s going to be bombarded with a thousand answers all saying something different, most telling her to install programs, and most telling her to use the command line. Because Linux is not an operating system, it’s a family of dozens of operating systems that can each be configured thousands of different ways.

If you tell her “I installed Fedora,” she’s going to run into the same issue, but on a lesser scale. At least there’s only a few hundred different ways on a per-distro basis.

If you tell her “I installed GNOME,” she will look up “how to change volume in GNOME,” and find her answer. But now you need to explain to her the difference between the three, and when to include that information in her searches, and she will ask “why could I just say ‘how to X in Windows?’ and didn’t have to memorize 3 different names for the same thing that all give me different answers???”

And yes, your grandma will just call you to ask anyway, but what about when it’s your friend trying to figure it out at 3 am and he can’t get ahold of you?

Meanwhile, the terminal is (more or less) distro-/DE-agnostic. So their options are to learn more about how is Opperating System formed than they’ll realistically ever need to know, or use the reviled terminal. Such is the plight of DIY OSes.

I daily drive Debian and it doesn’t require CLI for anything other than troubleshooting the problems I caused myself. There has been one time in 5+ years where it booted to console because the maintainers made changes to the kernel that fucked up the legacy nvidia drivers, and it had a workaround of booting to a previous kernel until they fixed it within the week. For newbies that might be scary the first time it happens, but its an easy fix that still didn’t require the CLI.

But nowhere did I say Linux required the terminal, I was addressing a different part of OP’s question. I guess since it’s such a prevalent myth, not denying it is tantamount to implicit agreement, so here’s me denying it.

CIA’s Simple Sabotage Field Manual

Why are people not revolting and asking questions

… they are tho??? Your question says more about you and the people you surround yourself with than it does about “people” in general.

If you’re asking why you don’t hear about it in the news or online, it’s because corporations, billionaires, and the government own mass media and control the narrative on there. The Revolution Will Not Be Televised, not because we’d rather have it streamed or printed in magazines, but because revolution is inherently antithetical to the purpose of The Spectacle

Liberate yourself from the need to have mass media give you permission to revolt.

full UI/UX behaviour that behaves almost identical to Windows/Mac

You want Windows or Mac.

If you want a computer that you can do stuff like web-browsing, document/spreadsheet/pdf/slideshow editing/creation, gaming, or multimedia processing on, there are distros and utilities on Linux that make those more-or-less easy and beginner-friendly,

BUT it requires divesting oneself of the habits, behaviors, and paradigms of other operating systems and being willing to learn anew. Community-based Libre software is developed in an entirely different way for an entirely different purpose; because of that, it is nearly impossible to recreate the same software as for-profit proprietary software. One is made by a community hacking together a functional system that suits their needs, the other is made to generate revenue, and thus has to keep users dependent on it by trapping them in dark patterns and igorance of its workings.

If you just want “Mac or Windows, but free as in beer,” suck it up, pay the devil his due, and buy one of those OSes. Libre Software is an entirely different paradigm, and thus requires a whole paradigm shift before anyone will be happy with it; on-boarding people who aren’t ready to divest themselves of the old paradigm just leads to disgruntled users who blame you for anything wrong with their PC, and creates a market void in the FOSS community ready to be filled by corpo proprietary slopware.

Windows hasn’t been “No CLI” since the requirements for TPM were added to Win 11 at the latest. Arguably, it’s been even longer if you wanted to get any customization beyond “changing window border colors and desktop background,” or if you wanted to do “hacker” stuff like remove start menu ads, but I guess most average users just didn’t bother.

Resentment aside, this is more attacking the letter of the query than the spirit. At best, OP admits the terminal isn’t bad and scary but still wants a distro that works best for GUI-focused people, at worst their eyes glazed over and they stopped reading everything you said after “when I was using it”

Reliable, clear release/support schedule: Debian Stable

Unlike Fedora Spins, most upstream distros don’t come with a DE pre-packaged, you choose it during the install process (or install a custom one from other sources post-install).

DEs currently offered by the Debian Installer include: Xfce, LXDE, LXQt, MATE, Lomiri, and of course Plasma and GNOME.

Not in the installer, but in the repository: Cinnamon, Budgie, Enlightenment, FVWM-Crystal, GNUstep/Window Maker, Sugar, “and possibly others” (according to the wiki).

You can also do what I do on my less-powerful laptops and just install a window-manager and associated utilities—just make sure to uncheck all DE options during install (you will be forced to use the console until you have a display server and window manager, tho). Right now I’m rocking i3 on my laptops; I would use Sway, but for some reason it’s more resource intensive.

Other offerings in the repository include: Openbox, Fluxbox, Compiz, Awesome, dwm, Notion, and Wmii

My personal recs are i3 (and recommended packages), Xfce, or MATE. I’ve used and liked all 3. I still use GNOME for my desktop, but those 3 are what I go with otherwise.

If you ain’t scared of the terminal and a little coding, you can use the format FireFox exports to. It’s a single html file with everything stored in one big <DL> with folders stored as headers and a sublist. All the urls and metadata are stored in the tags.

It should be relatively easy to make shell script that takes some arguments—e.g. action (add or remove), type (folder or link), url, and title—and modifies the file appropriately, programmatically taking metadata like creation/modify time (firefox stores them in unix time) from the system and favico from the website. That way it will work with any firefox anywhere.

If you want something more full featured, buku looks promising, although I haven’t tried it. For a gui keditbookmarks—which is a standalone, despite being part of KDE—looks like a simple interface that can import/export in firefox, opera, netscape, or Internet Explorer formats, as well as export to a “printable html file” (which I assume meets your definition of “readable”) and should open links in the system’s default browser.

I choose to use terminal because I can update my software without requiring a restart (I used Debian btw); for some reason, GNOME’s Software app cannot do this without restarting. I also prefer terminal-based text-editing for coding and scripting.

Depending on use-case, you can absolutely just use the distro without ever touching the terminal. It requires extra work to sift through all the online advice and docs that center around CLI commands though. The Average Windows User won’t be digging that deep in their system to customize the shit out of it like an Arch user, so they won’t need to touch the stuff that can only be accessed via command line. The Above Average Windows User will already be comfortable with the command prompt anyway.

Which distribution is the most user-friendly while still updated packages?

All of them? Why would a distro choose to be hostile to its users? (/s)

I assume you mean “beginner friendly”? In that case, I would stick to Debian: more stability than windows, harder to break than Arch, and lighter-weight than Fedora.

Those are the only 3 I’ve daily driven in the past couple of years, and that’s my takeaways. I can’t give informed input on any of the popular derivatives, except Ubuntu which I did use for awhile (back in 2014-2016): it was more prone to breaking shit than Debian, less beginner-friendly too (fuck Snaps, and fuck your Pro subscription data-harvesting up-selling bullshit).

Since you’re installing Debian, presumably you’ve done the required reading according to their wiki, and seen the DontBreakDebian page.

If not, here’s the portion I’m thinking of (emphasis mine)

Don’t make a FrankenDebian

Debian Stable should not be combined with other releases carelessly. If you’re trying to install software that isn’t available in the current Debian Stable release, it’s not a good idea to add repositories for other Debian releases.

First of all, apt-get upgrade default behavior is to upgrade any installed package to the highest available version. If, for example, you configure the forky archive on a trixie system, APT will try to upgrade almost all packages to forky.

This can be mitigated by configuring apt pinning to give priority to packages from trixie.

However, even installing few packages from a “future” release can be risky. The problems might not happen right away, but the next time you install updates.

The reason things can break is because the software packaged for one Debian release is built to be compatible with the rest of the software for that release. For example, installing packages from forky on a trixie system could also install newer versions of core libraries including libc6. This results in a system that is not testing or stable but a broken mix of the two.

Repositories that can create a FrankenDebian if used with Debian Stable:

• Debian testing release (currently forky)
• Debian unstable release (also known as sid)
• Ubuntu, Mint or other derivative repositories are not compatible with Debian!
• **Ubuntu PPAs and other repositories created to distribute single applications **

Some third-party repositories might appear safe to use as they contain only packages that have no equivalent in Debian. However, there are no guarantees that any repository will not add more packages in future, leading to breakage.

Finally, packages in official Debian releases have gone through extensive testing, often for months, and only fit packages are allowed in a release. On the other hand, packages from external sources might alter files belonging to other packages, configure the system in unexpected ways, introduce vulnerabilities, cause licensing issues.

Once packages from unofficial sources are introduced in a system it can become difficult to pinpoint the cause of breakage especially if it happens after months.

I would personally add that this isn’t a case of “if”, but rather “when”. Even if it works at the beginning, all it takes is Mint deciding they want to use a newer library when they update the package you’re using, and suddenly your system won’t boot and there’s no clear, easy solution other than “restore from backup.”

Even if you know what you’re doing, I would limit tinkering to binaries managed in the $HOME/.local/bin (and any applications that work as package management for that, like cargo, pip or homebrew) or packages that you completely control yourself (such as through git pulls and compiling yourself).

“Stick to the official repo” is generally the advice I would give for any distro, with the exception of DIY OSes that are intended to be patchwork, like gentoo or Arch.

THAT BEING SAID: I’m not saying “don’t install without a DE and piece your desired DE together from their parts.” Debian has a lot of DEs, window managers, and their individual parts all in the official repos; a lot of the difference you see between the versions Debian offers and the versions Mint or Ubuntu offer are basically just theming that you can do yourself without altering the system packages.

If you absolutely must install a 3rd party repo, just understand you are sacrificing Debian’s selling point of stability, and waiving your rights to hold the Debian Maintainers responsible; and when your system breaks (which might not be for many years), it will be entirely your own fault.

Since you can run the apps (glitchy as they may be), nothing is wrong with the read perms on the drive. Maybe write perms or exec perms? But ntfs perms don’t map neatly onto POSIX perms, so it’s hard to say. Maybe try setting the gid to the vboxuser group id and see if that helps?

You might also check out the mount manpage and look at the section about “Generic Mount Options”; this is the more in-depth explanation of the “options” column in fstab, and the defaults option (which depends on the distro) can hide stuff like nouser, which prevents users from mounting the drive.

Finally, look into ACLs and how to manage those for interoperability across Windows and POSIX systems.

Best case scenario, fixing it so your user has all access to the drive with the user,exec options fixes your issues. Otherwise, you’ve just gotta do the learning about ACLs and POSIX perms