Firstly this is clickbait since it's not actually Windows XP Mode (yes it's a VM but it's not the same thing as the original), also downloading and running PowerShell scripts from the internet is a recipe for disaster, you also don't need admin for this, you can just use a portable installation of VirtualBox and no admin would be required, my guess would be that running the installer trough PowerShell could've bypassed any security checks to do whatever he desires. Also you don't really know what the installer is doing, this could've been done trough a simple PowerShell script but instead he opted out for a installer which just makes it worse, you can simply install VB and download a Windows XP ISO and have the same exact thing. If you really care about people take this down, this is clickbait and can affect the security of everyone. EDIT: also why Windows XP x64? Wouldn't x86 version be enough, since the original XP Mode was created and used for compatibility and legacy programs and from my experience (and of others) Windows XP x64 was more of a concept than a daily OS, I remember it being really unstable and picky with drivers which is something you don't want for something like XP Mode which was used as a way to run legacy programs on top of an updated version of Windows so you could have the best compatibility but also security, but who cares about security when you run random PowerShell scripts from the internet with admin?

A closer parallel to XP Mode would be Unity Mode in VMware Workstation Pro. It lets you interact with programs within the guest operating system as if they were running on the host.

Could make this as a powershell script instead of a whole vb application in about 30 minutes, then I dont have to trust some unknown executable

So it's essentially just a preconfigured Windows XP VM... not much special about this. On top of that, it's really odd that they opted for the x64 edition for this. The whole point of the XP Mode in Windows 7 was legacy compatibility, and the x64 edition, with its limited driver library and complete lack of 16-bit software support, doesn't really offer much on that front compared to the native OS you're running. Regular 32-bit XP Pro would be a much better choice.

All this is VirtualBox with XP installed inside a VM. Why is there a need to use PowerShell to do this??

Comes with VBox Guest Additions already installed as well, very nice! Much nicer than any other XP VBox image I am seen so far! Side note: I'd turn off & disable Windows Update, System Restore and Remote Control functions/services at a minimum.

nah, just make a vm with windows xp.

There are comments saying this is clickbait, this is supposed to be a RECREATION of Windows XP Mode for Windows 7 made by Microsoft which was optional from 2009 to 2011. The one from Microsoft is also a VM. What do you think about that? I hope y'all understand.

the music and text reminds me of @endermanch

bit misleading calling it the hard way, but great tutorial! i definitely liked the manual for this situation because of how detailed it got regarding everything from drivers to partitions, it's a great read! great video!!

Pro tip: do NOT run random Powershell commands that you don't know what they do and "just confirm the UAC prompt" just because a random KZfaqr tells you to.

That's... Just a VM

CLICKBAIT ALERT!!!

It’s just a VM, I don’t understand how it’s a “XP” mode if it’s just a VM

Cool video!

Nice video! Keep going man, oh yeah i sub on you :). And nice music

does required tpm2.0 secure boot etc...??

3:49 N I N E C I R C L E S

It's time people move on from Windows 7 and 10. Go to Linux or something else.

10.2023 ......

This is how I installed Arch on my laptop, archinstall should only be used for quickly spinnning up VMs, test environments or whatever. The way I did it was to install the base system first, get that bootable and make sure networking works, and then install KDE after I was able to boot and connect to networking while booting from internal storage

People think this is hard try installing Gentoo

Usually you should to use an uppercase G in the useradd command, otherwise it's not going to create the related group for your user. And when installing plasma, it's better to install the meta package, e.g. plasma-meta, and one or more meta packages for groups of applications. Otherwise you have a lot more work installing literally every piece separately, and then it's a lot easier to miss some important things. This also applies to other desktops, and in fact also to other packages on other Linux distributions.

in Rihanna's voice : SO MAYBE I'M A MASOCHISTTTTTTTTT😆😆😆😆

Isn't that the normal way? Using a script poses a serious security risk and you don't even qualify for help in the forums.

1:07

Done

I think you *should* install Arch the manual way at least the first or second time. It is basically the tutorial. If you don't really know how Arch is installed, you wont have as good of a time diagnosing when it breaks, and install scripts also sometimes can break themselves. Installing Arch manually in a vm multiple times before trying it, also taught me generally how everything in it works and made me very familiar with the command-line. If I didn't do that, I probably would've given up on Arch already. EDIT: Some extra thoughts after I have fully watched the video. This install of Arch *will* run, yes, but its definitely not good and there are quite a few things that should be done differently or you might have some massive issues, so I wouldn't recommend the video as a guide. I''ll go through most of them: 1 and 2. No swap and home partition. SWAP is considered optional, however the kernel *will* crash if you cap out on ram without it, and some apps will just use swap memory. Its considered backup memory, so if you dont have it and you have an app that only uses swap, it wont start or be very buggy. A separate /home partition isnt as severe, but makes separating user data from the actual core of the machine much more difficult. 3. Not critical, but you could have installed pacman-contrib in the live iso, backed up the iso's mirrorlist through cp to a .backup, then run "rankmirrors -n 6 /etc/pacman,d/mirrorlist.backup > /etc/pacman.d/mirrorlist. This will speed up downloading the core system of Linux drastically. 4. After installing the base system, there are two options in pacman.conf that you NEED to turn on if you're gonna use the system more then once. [multilib] and include= just below it then run pacman -Syu. This enables 32 bit support. Also you can download bash-completion to make commandline life a little easier. 5. You forgot 2 packages: linux-headers and efibootmgr. linux-headers in particular is heavily recommended if its not just a virtualmachine, and efibootmgr is quite useful for managing your boot order, setting certain things to be unbootable or bootable, and even manually adding boot entries. 6. The fstab file isnt just used for drive errors, its used to tell the kernel what drives to actually mount at boot time. Very critical if you have more then just /boot and root. You should also use one > instead of two >> for creating the fstab file (or redoing it) cause duplicate entries from >> can cause fstab parse errors. 7. Please, for your own sake do NOT manually edit /etc/sudoers! This has a very high chance of breaking the sudo command. Instead, use "EDITOR=nano visudo" to edit the proper file for it. It even TELLS you not to do this at the top of the file, but you skipped over it immediately. (I don't blame you, it is easy to miss, but please read the tops of files! especially with Arch) 8. You did not add your user to storage,power as well after wheel, (you need capital -G instead of lowercase -g for multiple) and you did not specify a command shell, im not sure if it defaults to /bin/bash but just in case you should always add (after wheel,storage,power) "-s /bin/bash" then your username. If it doesn't use /bin/bash as default then uh.. good luck, no command shell. the storage group also lets you configure and use storage devices, and power lets you configure power management, so they are important. 9. You made a mistake specifically at 2:57, and while it is easy to overlook, you should have used an underscore instead of a dash for en-US, when it should be en_US. This won't break your system, but it can (and probably will) break applications. You can also tell that your LANG= setting is not registering properly, because neofetch and fastfetch both have Locale= at the bottom. When specified correctly and rebooted, it should show "Locale=en_US.UTF-8" at the bottom. 10. Not actually an issue, but instead of using && and rewriting the systemctl enable and start, you can just use "systemctl enable --now" to both enable and start the service. You also don't need to restart unless you just use enable, start and enable --now are both adequate. Its just a thing to help save time typing into a black box. That is all of them that I have immediately noticed. These aren't a bad thing, generally installing arch manually is difficult but when you fully learn it it becomes much faster to do.

Cool video!

Paint thinner! (Because everyone says Windows 11 is just 10 with a coat of paint.)

why not vmware?

at this point just use windows 10

3:50 GD reference?