Please open Telegram to view this post
VIEW IN TELEGRAM
❤134🤔6👍5😢4😱2🤬1
😵💫 Failing to upload
It's been a while, so I made a huge video... only to realize I have to remake it. It's demoralizing as hell.
Just a perfect storm today — here's part of footage I recorded for the huge video I mentioned.
fml
It's been a while, so I made a huge video... only to realize I have to remake it. It's demoralizing as hell.
Just a perfect storm today — here's part of footage I recorded for the huge video I mentioned.
fml
YouTube
A Great Functioning Installer
I promised to upload a video tonight, but then I realized I have to remake the entire video... fml
https://enderman.ch
https://enderman.ch
😢69👍4🤔1🤬1
Pressing Ctrl + Shift + J in the Windows OOBE opens a full-fledged JavaScript developer console.
Watch the source code review to learn more.
Who's getting fired tonight? 😊
Please open Telegram to view this post
VIEW IN TELEGRAM
❤87😱21👍7🎉6🤔4🤬1
Pressing Ctrl + Shift + D in the Windows OOBE opens «Autopilot diagnostics» — the configuration and deployment information for the current setup.
It's an incredibly helpful tool for OEMs and anyone bulk deploying Windows.
Please open Telegram to view this post
VIEW IN TELEGRAM
🤔51👍18❤5🤬1
Pressing the Windows key 5 consecutive times in the Windows 11 OOBE brings up the «provisioning menu».
Provisioning is slightly different to customizing an image and then deploying it. It's intended for a different purpose: you have to supply a provisioning package (a .ppkg file) with configuration settings every time you install Windows, whereas customizing the image prior to deployment locks the changes in and predetermines the configuration from the very beginning of the install.
An illustrative use case of provisioning is when one owns a medium-sized industry with a few hundred employees split into subdivisions, and each subdivision has its own Windows configuration. Creating multiple images makes no sense here — it's overkill for such a task. It's much easier to use a provisioning scenario.
Please open Telegram to view this post
VIEW IN TELEGRAM
Please open Telegram to view this post
VIEW IN TELEGRAM
🤔44❤6👍6😱1🤬1
🔍 Zoomies
Guess what, the Windows OOBE isn't immune to zooming in and out of it either.
The edge cases look hilarious. That's clearly unintended behavior, because the zoom is already covered by the «Ease of Access» feature set — there's Magnifier.
It's safe to say the Windows OOBE is a web application, so the zoom feature is enabled by default without any XAML props, which was the case with Windows 10 notifications.
Pasting continues... 📋
Guess what, the Windows OOBE isn't immune to zooming in and out of it either.
The edge cases look hilarious. That's clearly unintended behavior, because the zoom is already covered by the «Ease of Access» feature set — there's Magnifier.
It's safe to say the Windows OOBE is a web application, so the zoom feature is enabled by default without any XAML props, which was the case with Windows 10 notifications.
Pasting continues... 📋
🤔50😱11👍8❤5🤬2
🖼 The Windows OOBE background
The background gradient in the OOBE is actually inherited from the desktop background of the current user invoking the OOBE, except it's blurred out into a gradient at 100% zoom. Zooming out completely pretty much gives it away, as can be seen in the previous post.
Since the OOBE is running in the context of defaultuser0, you can change the background by setting a different desktop background image for defaultuser0 respectively.
Here's how the dark mode wallpaper looks along with the OOBE! Therefore, the dark mode for the Windows 11 OOBE is technically possible, except it requires quite a bit of CSS tweaking and removing that atrocious 4500x3000@30fps intro video with a pure white background.
The background gradient in the OOBE is actually inherited from the desktop background of the current user invoking the OOBE, except it's blurred out into a gradient at 100% zoom. Zooming out completely pretty much gives it away, as can be seen in the previous post.
Since the OOBE is running in the context of defaultuser0, you can change the background by setting a different desktop background image for defaultuser0 respectively.
Here's how the dark mode wallpaper looks along with the OOBE! Therefore, the dark mode for the Windows 11 OOBE is technically possible, except it requires quite a bit of CSS tweaking and removing that atrocious 4500x3000@30fps intro video with a pure white background.
😱32🤔13👍11❤5🤬1
💻 The reasoning behind Windows 11 requirements
The Windows OOBE intro is actually a 4500x3000@30fps video file. Microsoft strategically encoded it to take up only 580KB, which isn't all too surprising.
However, they chose the worst way of dealing with simple animation. Whenever the animation isn't too complicated and the logo is basically 4 coplanar squares, it's a rule of thumb in web development to use vector graphics with CSS transitions.
The only logical reason why they made such a dead simple animation into a video I can think of is potential for a custom OEM intro video. I'm giving Microsoft the benefit of a doubt here, however, that doesn't seem to be a documented «feature». But it's not rocket science either. I say it's inconclusive.
If this is what the minimum requirements were artificially bumped up for, I strongly advocate against that decision.
The Windows OOBE intro is actually a 4500x3000@30fps video file. Microsoft strategically encoded it to take up only 580KB, which isn't all too surprising.
However, they chose the worst way of dealing with simple animation. Whenever the animation isn't too complicated and the logo is basically 4 coplanar squares, it's a rule of thumb in web development to use vector graphics with CSS transitions.
The only logical reason why they made such a dead simple animation into a video I can think of is potential for a custom OEM intro video. I'm giving Microsoft the benefit of a doubt here, however, that doesn't seem to be a documented «feature». But it's not rocket science either. I say it's inconclusive.
C:\Windows\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\media\oobe-intro.mp4If this is what the minimum requirements were artificially bumped up for, I strongly advocate against that decision.
🤔51😱13❤5🤬5👍3
Enderman
💻 The reasoning behind Windows 11 requirements The Windows OOBE intro is actually a 4500x3000@30fps video file. Microsoft strategically encoded it to take up only 580KB, which isn't all too surprising. However, they chose the worst way of dealing with simple…
This media is not supported in your browser
VIEW IN TELEGRAM
The original intro video pulled directly from the build 26052 install.wim file, so you can judge for yourself.
Please open Telegram to view this post
VIEW IN TELEGRAM
👍44😱8❤5🤬2