WEBVTT

00:00:00.520 --> 00:00:04.639
oh hold up there hot stuff

00:00:06.200 --> 00:00:13.799
ID core to Duo get get out of here with

00:00:10.519 --> 00:00:16.359
this trash this is Windows 11 an

00:00:13.799 --> 00:00:21.119
exclusive club for only PCS running the finest

00:00:18.439 --> 00:00:25.840
Hardware all right listen you look like a cool kid I'm

00:00:24.119 --> 00:00:27.960
going let you in on a secret way you can get

00:00:28.800 --> 00:00:34.600
in just just like I'm going let you in on our sponsor Ridge wallet has

00:00:32.920 --> 00:00:38.360
redefined the traditional wallet with its compact frame and RFID blocking

00:00:36.480 --> 00:00:42.360
plates get yours today and keep your wallet bulge down using offer code Linus

00:00:40.440 --> 00:00:45.760
to save 10% and get free worldwide shipping we're going to have it linked

00:00:43.600 --> 00:00:49.760
below if you're anything like I don't know most Gamers you were probably

00:00:47.800 --> 00:00:55.480
outraged when Microsoft announced that Windows 11 wouldn't officially support

00:00:52.320 --> 00:00:58.079
any CPU released before about 2017 but

00:00:55.480 --> 00:01:02.000
as usual the whole story is a little bit more complicated than that by far the

00:01:00.600 --> 00:01:07.600
easiest way to get up and running with Windows 11 today is the official one an

00:01:05.040 --> 00:01:11.560
inplace upgrade via The Insider program sign into your Microsoft account in

00:01:09.439 --> 00:01:15.759
Windows 10 follow the steps to register online enroll your device in the

00:01:13.119 --> 00:01:19.680
settings Pane and choose the dev Branch just make sure that optional Diagnostics

00:01:17.439 --> 00:01:24.159
reporting is enabled restart your PC and if all goes well you should get Windows

00:01:21.400 --> 00:01:29.400
11 as an update but what if it doesn't go well well chances are that you don't

00:01:26.560 --> 00:01:36.320
have secure boot enabled or your TPM isn't enabled abled or both okay but

00:01:33.399 --> 00:01:40.640
what are those and why do we need them I'm glad you asked you probably heard of

00:01:38.360 --> 00:01:44.680
them by now but the TPM or trusted platform module isn't new it's a pretty

00:01:43.119 --> 00:01:48.640
simple device that generates and stores cryptographic keys to help protect

00:01:46.320 --> 00:01:53.119
encrypted data and credentials Microsoft has actually required them for System

00:01:50.280 --> 00:01:57.799
integrators since July of 2016 but they're far less common in the DIY space

00:01:55.600 --> 00:02:01.399
because for a long time the only way to get one was to add it to your

00:01:59.159 --> 00:02:05.759
motherboard with a tiny little PCB like this one it plugs neatly into a keyed

00:02:03.560 --> 00:02:10.200
header and the job is done but that assumes you can find a compatible one in

00:02:07.880 --> 00:02:14.080
the first place traditionally very few shops have carried them and there's at

00:02:11.680 --> 00:02:18.640
least three different pinouts from ASUS alone with everyone seeming to have

00:02:16.760 --> 00:02:24.920
different ideas about how to implement them or or not compact ITX motherboards

00:02:22.200 --> 00:02:28.879
often omit it all together this lack of standardization has made them tough to

00:02:27.040 --> 00:02:33.680
find even before Microsoft announced you needed one and I mean even ASUS could

00:02:31.120 --> 00:02:37.959
only find one in their us office at all so thankfully I had one of my own to

00:02:35.640 --> 00:02:42.159
bring in the good news is that TPMS have been built into the firmware of our

00:02:39.040 --> 00:02:43.920
motherboard since around 2015 so chances

00:02:42.159 --> 00:02:48.239
are you might have one already and not even know it but uh these ones have the

00:02:46.120 --> 00:02:52.840
disadvantage of being tied to the CPU and many will clear their keys when you

00:02:49.959 --> 00:02:57.040
factory reset or update the BIOS derp manufacturers like ASUS say they'll be

00:02:54.599 --> 00:03:01.159
enabling it by default going forward but until Windows 11 this firmware TPM has

00:02:59.680 --> 00:03:05.319
been been disabled by default on most DIY boards that's because in order to

00:03:03.480 --> 00:03:10.120
use a TPM module like this that you install yourself you have to disable the

00:03:07.120 --> 00:03:11.920
firmware TPM and vice versa these days

00:03:10.120 --> 00:03:15.560
TPM is mostly important for features like Windows hello and bit Locker Drive

00:03:13.920 --> 00:03:19.360
encryption so it's no surprise that it's becoming more relevant as they become

00:03:17.360 --> 00:03:22.480
more popular there's also additional security that can be gained through

00:03:20.599 --> 00:03:26.319
using a TPM in conjunction with Intel's management engine and AMD's platform

00:03:24.159 --> 00:03:32.040
security processor and this is important for Windows 11 more on that later well

00:03:29.360 --> 00:03:37.200
all right right TPMS are good but why does Windows need it short answer it

00:03:34.799 --> 00:03:40.640
doesn't if you install Windows 11 or Windows 10 for that matter and then

00:03:39.080 --> 00:03:44.799
disable it you just need to reenroll your Windows hello credentials and use

00:03:42.080 --> 00:03:49.159
your bit Locker backup key you did keep that key right but what about secure

00:03:46.879 --> 00:03:54.760
boot short answer it can provide a security boost in Windows by blocking

00:03:50.799 --> 00:03:56.720
non whql or non-certified drivers long

00:03:54.760 --> 00:04:00.480
answer it ensures your operating system and drivers are what they say they are

00:03:58.239 --> 00:04:04.319
when your PC boots and Microsoft mandates that their Partners include

00:04:02.079 --> 00:04:08.200
Microsoft keys by default so all you need to do is turn it on and it should

00:04:05.879 --> 00:04:11.120
start working of course this has some fun implications for alternative

00:04:09.680 --> 00:04:15.519
operating systems that aren't willing to use their keys now as of filming

00:04:13.239 --> 00:04:20.000
toggling secur boot off or installing without it doesn't really have any

00:04:17.440 --> 00:04:26.040
effect on being able to run Windows 11 so again good for security in theory but

00:04:23.840 --> 00:04:29.400
this is another non-requirement and one you'd probably want to keep off if you

00:04:27.639 --> 00:04:33.080
want to play with Linux or something if you do do want to turn it on then good

00:04:31.280 --> 00:04:38.400
news most computers released since Intel's thirdd gen core support secure

00:04:34.960 --> 00:04:40.440
boot bad news not all Windows installs

00:04:38.400 --> 00:04:46.120
done since then will support it secure boot only works with pure UEFI mode so

00:04:43.840 --> 00:04:50.120
if you're using Legacy Windows install or even if you just have CSM enabled in

00:04:47.960 --> 00:04:53.039
the BIOS you're incompatible you can check which you're running and whether

00:04:51.440 --> 00:04:57.479
secure boot is enabled or not using the system information app if secure boot

00:04:54.880 --> 00:05:01.039
State shows on then you're good and if it doesn't and your BIOS mode shows uaf

00:04:59.759 --> 00:05:05.320
F then all you need to do is turn on secure boot in your BIOS sometimes this

00:05:03.240 --> 00:05:10.080
is done by just installing default Keys rather than just a toggle but uh if the

00:05:07.680 --> 00:05:14.280
BIOS mode says Legacy you'll need to do some more work first make sure your BIOS

00:05:12.520 --> 00:05:18.039
can enable secure boot at all it should have its own section usually under the

00:05:16.039 --> 00:05:21.479
security or boot menus don't actually enable it yet though first we need to

00:05:19.680 --> 00:05:25.919
prepare Windows by using a built-in tool called mbr2gpt go to settings then find

00:05:24.479 --> 00:05:29.479
the recovery pane under update and security and click restart now under

00:05:27.479 --> 00:05:33.680
Advanced startup choose troubleshooting then Advanced options then command

00:05:31.280 --> 00:05:37.880
prompt then type this command into the command prompt window and hit enter if

00:05:35.840 --> 00:05:43.400
all goes well it should say validation completely successfully from here type

00:05:40.280 --> 00:05:46.400
mbr2gpt /on convert to convert the

00:05:43.400 --> 00:05:49.199
install from Legacy to ufi once that's

00:05:46.400 --> 00:05:52.759
done close the window and reboot now you can turn on secure Boot and enjoy neat

00:05:50.759 --> 00:05:56.840
ufi features like this handy ufi firmware settings button in the advanced

00:05:54.319 --> 00:06:01.759
startup menu of course we promised there was a back door remember so uh don't

00:05:59.360 --> 00:06:07.680
worry if you don't have secure boot or UEFI or even a TPM for that matter there

00:06:04.720 --> 00:06:12.400
is still a Way Forward which brings up an important question how can Microsoft

00:06:10.160 --> 00:06:17.560
justify having us jump through all these extra Hoops well Microsoft's analytics

00:06:15.400 --> 00:06:22.280
reportedly showed that surface devices equipped with a TPM and secure boot as

00:06:20.319 --> 00:06:29.160
part of virtualization based security reported up to 60% fewer instances of

00:06:25.280 --> 00:06:30.840
malware infection that's pretty huge and

00:06:29.160 --> 00:06:34.960
even though you can get this level of security in Windows 10 today it makes

00:06:33.360 --> 00:06:39.479
sense that Microsoft would want to make that change mandatory for what they're

00:06:36.680 --> 00:06:44.800
calling the most secure Windows ever especially if they want to keep Windows

00:06:41.120 --> 00:06:46.919
competitive with macOS and Chrome OS so

00:06:44.800 --> 00:06:50.720
in my mind if you're running a system with those security features available

00:06:48.960 --> 00:06:56.240
there is no question that you should enable them it's free security but the

00:06:53.759 --> 00:07:00.000
problem is that many people don't have those features available and that's why

00:06:58.000 --> 00:07:04.759
there's been so much concern about these system requirements but there's hope if

00:07:02.479 --> 00:07:08.120
you don't quite meet them for our first trick we're going to get into The

00:07:06.039 --> 00:07:12.479
Insider program with unsupported Hardware you will still need a TPM for

00:07:10.520 --> 00:07:16.520
this Windows checks for one at the last mile while downloading but a little bit

00:07:14.560 --> 00:07:20.400
of registry hacking will bypass the hardware compatibility checks just

00:07:18.759 --> 00:07:25.319
enroll with The Insider program as before then when you see that your only

00:07:22.560 --> 00:07:29.720
choice is the release preview Branch play along for now reboot and then when

00:07:27.879 --> 00:07:34.479
you get back to the desktop go go ahead and launch redit navigate to this key

00:07:32.560 --> 00:07:39.680
and change these values to read like this then navigate to this key and

00:07:36.879 --> 00:07:44.960
change these values they're basically the same things but pay attention to the

00:07:42.080 --> 00:07:48.280
names once that's done reboot and look at The Insider program settings pane

00:07:46.599 --> 00:07:53.199
again you should now be enrolled and able to download the Windows 11

00:07:50.440 --> 00:07:57.840
update with the major caveat that you are not allowed to update to the final

00:07:55.280 --> 00:08:03.080
release when it drops so if you want to run the full version when it releases

00:08:00.199 --> 00:08:07.479
watch on the solution here is to use the same method that's used to install a

00:08:04.840 --> 00:08:12.599
fresh copy of Windows 11 on unsupported Hardware an ISO now as of filming

00:08:10.440 --> 00:08:16.840
Microsoft has yet to make one officially available but that doesn't mean that you

00:08:14.759 --> 00:08:22.199
can't make one yourself they already provide the files that you need so using

00:08:19.240 --> 00:08:25.960
uup dump you can select Windows 11 then choose the additions that you want to be

00:08:23.840 --> 00:08:30.159
included this next screen is a bit confusing but the tldr is that we want

00:08:27.919 --> 00:08:35.640
to choose this option to add a and then this option to create an ISO

00:08:32.120 --> 00:08:38.000
with install.esd instead of install.wim

00:08:35.640 --> 00:08:42.360
Click create download package and you'll be given a zip file that is way smaller

00:08:39.959 --> 00:08:47.200
than an ISO that's because what we downloaded is just a script that

00:08:44.480 --> 00:08:52.000
downloads and creates the iso for you straight from Microsoft not from a third

00:08:50.000 --> 00:08:55.720
party the script is readable so you can verify it for yourself before running it

00:08:53.880 --> 00:08:59.120
if you like this will take a while though so let the tool do its thing

00:08:57.640 --> 00:09:03.120
while you go grab a snack or maybe browse LTT Store.com for a cool new

00:09:01.200 --> 00:09:07.600
t-shirt like this one once you have a Windows 11 ISO you can either burn it to

00:09:05.079 --> 00:09:12.440
a disc or extract its contents to a USB flash drive boot from it and you'll see

00:09:09.800 --> 00:09:16.800
a very familiar screen from there on it's just one more familiar trick to let

00:09:14.279 --> 00:09:21.760
us install on any system we want even so-called incompatible ones hold shift

00:09:19.839 --> 00:09:26.560
and press F10 to make a command prompt window appear then type reg edit and

00:09:24.279 --> 00:09:33.320
navigate to this registry key right click on it and make a new key called

00:09:28.720 --> 00:09:36.120
lab fig in here create two dword values

00:09:33.320 --> 00:09:41.079
bypass TPM check and bypass secure boot check and set them both to one close reg

00:09:38.760 --> 00:09:45.040
edit and the command prompt and continue on your Merry way now we're not sure if

00:09:43.200 --> 00:09:49.480
Microsoft will continue to allow this registry hack After official release

00:09:47.360 --> 00:09:54.279
they did say though that some OEM and Integrated Systems will be exempt and

00:09:51.880 --> 00:09:58.880
presumably this is how they'll do it but it is Microsoft and you never know so if

00:09:57.200 --> 00:10:03.760
it does stop working by the time Windows 11 is released you can work around it in

00:10:01.399 --> 00:10:09.320
one of two other ways both using a Windows 10 ISO first you copy this dll

00:10:07.800 --> 00:10:14.680
file from the sources folder of a Windows 10 ISO into the sources folder

00:10:11.760 --> 00:10:19.480
of a Windows 11 ISO this file contains the compatibility checks so because they

00:10:17.519 --> 00:10:24.560
didn't exist in Windows 10 you're able to use that same compatibility check for

00:10:21.800 --> 00:10:28.399
Windows 11's installer it is possible that Windows 11's installer will change

00:10:26.519 --> 00:10:33.399
before release however so the more futureproof method is to go the other

00:10:30.839 --> 00:10:39.160
way around this time copy the install.esd file from the sources folder

00:10:36.200 --> 00:10:45.279
of the Windows 11 ISO into the sources folder of the Windows 10 ISO and Bam

00:10:42.800 --> 00:10:52.560
that Windows 10 ISO is now a fully functional Windows 11 installer it even

00:10:48.200 --> 00:10:55.680
works for legacy systems without ufi but

00:10:52.560 --> 00:10:57.600
wait hold on a second why does this work

00:10:55.680 --> 00:11:02.519
the Windows setup process uses a tool called dism or for deployment image

00:11:00.240 --> 00:11:06.200
servicing and management fundamentally the Windows installation files are just

00:11:04.760 --> 00:11:10.079
a dis image that is applied to the Target disc when installing this makes

00:11:08.200 --> 00:11:13.959
for a very clean and easily verified install and it makes it far easier to

00:11:12.279 --> 00:11:17.839
generate custom images that can then be installed on multiple PCS complete with

00:11:16.200 --> 00:11:21.639
the normal first-time setup it's how system integrators like Dell and HP make

00:11:19.680 --> 00:11:25.200
their customized Windows installs the setup program isn't actually doing

00:11:23.639 --> 00:11:29.720
anything more than prepping your drive and applying the image to it it doesn't

00:11:27.480 --> 00:11:33.760
care what's in the image garbage in garbage out Windows 11's installer

00:11:31.959 --> 00:11:37.760
simply has some visual changes compared to 10's and of course those extra checks

00:11:36.200 --> 00:11:42.480
to make sure you're using a TPM and secure boot so putting the Windows 11

00:11:40.040 --> 00:11:46.120
install image onto a Windows 10 ISO bypasses all of Windows 11's new

00:11:44.360 --> 00:11:49.959
installation requirements the rest of this phase of the install process is the

00:11:47.880 --> 00:11:53.760
same as Windows 10 enter a product key if you have one pick your addition

00:11:51.880 --> 00:11:58.399
choose a rid driver if needed select which drive to install to and format it

00:11:56.040 --> 00:12:01.600
if necessary when the installer finishes Windows will boot up with a pretty

00:11:59.920 --> 00:12:07.360
animation and greet you with a region and language selection screen followed

00:12:03.320 --> 00:12:09.200
by an update naming the PC and a reboot

00:12:07.360 --> 00:12:13.160
a word of warning though once it's back up it'll ask you for your Microsoft

00:12:11.160 --> 00:12:18.720
account and there is no way of skipping that on Windows 11 home edition sort of

00:12:16.959 --> 00:12:22.320
as of right now you can actually just unplug the Ethernet cable before it

00:12:20.519 --> 00:12:25.880
reboots and it will let you set up a local account instead I wouldn't count

00:12:24.519 --> 00:12:29.959
on this working in the future though because Microsoft has indicated that an

00:12:27.760 --> 00:12:33.600
internet connection will be required for home edition moving forward although

00:12:32.360 --> 00:12:37.760
there's nothing that would prevent you then from unlinking your Microsoft

00:12:35.360 --> 00:12:41.760
account after the initial setup at least for now because there's no way to know

00:12:40.040 --> 00:12:46.399
if it will stay that way in the future in Windows 11 Pro though you can just

00:12:43.800 --> 00:12:49.760
choose to never input one on the plus side if you do sign in with a Microsoft

00:12:48.320 --> 00:12:53.360
account you get to choose whether to restore apps and settings from a backup

00:12:51.600 --> 00:12:57.199
of your previous install kind of like Android although the apps they're

00:12:55.160 --> 00:13:00.920
talking about are Windows store apps but you also get to choose privacy options

00:12:58.880 --> 00:13:05.160
just like you do in Windows 10 today and then after a short setting up period you

00:13:02.680 --> 00:13:08.760
will be at the Windows 11 desktop speaking of which get subscribed because

00:13:06.920 --> 00:13:14.399
we're planning a deeper dive into what's new with Windows 11 and you are not

00:13:10.399 --> 00:13:16.800
going to want to miss it but hang on if

00:13:14.399 --> 00:13:22.680
you can ignore the security requirements and just install Windows anyway what are

00:13:19.760 --> 00:13:26.440
the real system requirements well it might not surprise you that we can go

00:13:24.360 --> 00:13:33.120
back farther than Microsoft's officially listed coffee Lake and Zen plus CPUs how

00:13:29.560 --> 00:13:35.480
about a fourth gen CPU from 2013 not far

00:13:33.120 --> 00:13:40.639
enough back for you how about this core2 Duo e8400 from

00:13:38.199 --> 00:13:46.199
2008 yeah that's right it's running Windows 11 without even a ufi BIOS this

00:13:44.399 --> 00:13:50.480
was about as far back as we could go though without running into serious

00:13:47.680 --> 00:13:56.199
issues the single core Pentium 4630 that we tried should have supported the 64bit

00:13:53.399 --> 00:13:59.959
instructions necessary to run the OS but it ended up just hard resetting every

00:13:58.040 --> 00:14:04.839
time we tried to run it even the installer a single core Athlon 64 might

00:14:02.880 --> 00:14:10.839
be okay but we don't have one of those handy to test with so clearly the system

00:14:07.600 --> 00:14:13.079
requirements are nonsense but here's the

00:14:10.839 --> 00:14:17.759
thing what you guys might know is that these Shenanigans with minimum system

00:14:15.120 --> 00:14:25.040
requirements are nothing new Microsoft actually lists a fifth gen core CPU as

00:14:21.199 --> 00:14:27.800
the oldest that can run Windows 7 I mean

00:14:25.040 --> 00:14:33.920
that's clearly not true Windows 7 came out over 5 years before those CPUs even

00:14:31.199 --> 00:14:38.120
existed so what's up with that well the Keeny among you might have spotted a

00:14:35.639 --> 00:14:43.399
pattern here between Windows 10 and Windows 11 Microsoft tested and

00:14:40.519 --> 00:14:48.160
validated only CPUs from as old as one or two years prior to the release of

00:14:45.600 --> 00:14:53.839
each and this is what you're seeing on the official support lists validation

00:14:52.040 --> 00:14:58.160
Microsoft made a blog post recently saying as much calling out security

00:14:56.000 --> 00:15:02.519
reliability and compatibility specifically as guided principles

00:15:00.240 --> 00:15:07.240
they're apparently looking into zen1 and kbl Lake CPUs now after seeing so much

00:15:04.720 --> 00:15:12.240
backlash from consumers by the way so that's pretty cool and it's not that

00:15:10.199 --> 00:15:16.040
Microsoft is recommending the CPUs that they are simply because they're lazy and

00:15:14.320 --> 00:15:20.399
they didn't feel like testing more Windows 11 makes it an official

00:15:18.079 --> 00:15:25.399
recommendation and as far as I can tell a requirement for oems going forward to

00:15:23.000 --> 00:15:31.079
use a new driver model called Windows drivers which Microsoft Claims can

00:15:27.560 --> 00:15:34.759
reduce driver related crashes by

00:15:31.079 --> 00:15:36.680
99.8% that would be great but the

00:15:34.759 --> 00:15:40.720
downside is that a new driver model means that they're probably going to

00:15:38.040 --> 00:15:45.680
need new drivers assuming that they disallow the previous driver model at

00:15:42.639 --> 00:15:48.759
some point well this is where the eth

00:15:45.680 --> 00:15:51.360
Gen core and ryzen 2000 recommendations

00:15:48.759 --> 00:15:56.240
come from the hardware surrounding those chips is still officially supported by

00:15:53.880 --> 00:16:01.519
their vendors and is likely to get Windows 11 drivers while the same is not

00:15:58.639 --> 00:16:07.040
NE necessarily true for CPUs from 20177 or earlier so AMD and Intel actually

00:16:04.639 --> 00:16:11.959
have their own role to play here in this artificial lockout of older but not very

00:16:09.600 --> 00:16:15.680
old Hardware all of which is to say then that at least for now you can install

00:16:13.680 --> 00:16:22.440
Windows 11 on basically anything that you would want to but the experience

00:16:18.160 --> 00:16:24.519
might be subpar and might get sub parer

00:16:22.440 --> 00:16:28.040
in the future according to Microsoft it'll be best to run on something newer

00:16:26.519 --> 00:16:32.560
for official support both from the vendor and from them but at the end of

00:16:30.959 --> 00:16:36.800
the day if you're worried you won't be able to install Windows 11 don't be

00:16:35.079 --> 00:16:42.000
Microsoft hasn't locked it down the way that we feared at least not yet this

00:16:40.199 --> 00:16:46.399
video is brought to you by manscaped in their lawnmower 4.0 which is the perfect

00:16:44.440 --> 00:16:51.279
companion for keeping your goods looking trim neat and clean the new lawnmower

00:16:49.199 --> 00:16:55.199
has ceramic blades with skin safe technology reducing Nicks and cuts and

00:16:53.560 --> 00:16:59.000
it can be easily replaced with a fresh blade their new wireless charging system

00:16:57.279 --> 00:17:02.639
removes the need to bring cables with you and is compatible with most G

00:17:00.800 --> 00:17:06.480
charging pads it's cordless and waterproof gets 90 minutes of use on a

00:17:04.520 --> 00:17:11.000
full charge and includes four different trimmer guards so get 20% off plus free

00:17:09.240 --> 00:17:15.160
international shipping using the promo code Tech at the link below so thanks

00:17:13.720 --> 00:17:18.919
for watching guys go check out our recent video where we gamed on the

00:17:16.959 --> 00:17:23.600
leaked build of Windows 11 very impressed at how well it was running

00:17:21.160 --> 00:17:28.120
even before they announced it it a different kind of video more of an

00:17:24.919 --> 00:17:28.120
exploration thing you know