windows

winget install PrestonN.FreeTube

⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿

Winget (The App Replicator)

If PnPUtil is for your drivers, Winget is for your apps.

The "Hacker" Move:

winget export -o C:\setup\apps.json

Why it's useful: On a clean build, you don't want to hunt for .exe files. You just run winget import -i D:\setup\apps.json.

The Result: Windows will automatically download and install every app on your list (Chrome, Docker, VS Code, etc.) in the background while you do something else.

⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿

#PnPUtil (The Driver "Savior")

#Why it's productive: It saves a copy of every working driver on your system into one folder. If anything breaks while you're offline, you can point #Windows to that folder and be back online in seconds.

pnputil /export-driver * C:\DriverBackup

#The import

pnputil /add-driver "D:\DriverBackup\*.inf" /subdirs /install

⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿ ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿

winget install Microsoft.PowerToys --source winget

⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿

desktopinfo

Official URL: https://www.glenn.delahoy.com/desktopinfo/

folder is in programs and you can copy a shortcut to startup

⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿

wiztree

1. The Official Website

The official URL is: diskanalyzer.com

⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿

localsend

Where to get it: localsend.org

⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿

Gemini said

Absolutely. This is one of the most common uses for FFmpeg—hitting a specific "target size" (like 3.9GB) to fit on a FAT32 thumb drive or meet an upload limit.

To do this accurately, you move away from the "Quality" slider (-crf) and use Two-Pass Encoding.

The Strategy

You can't just tell FFmpeg "make this 4GB." You have to calculate the Bitrate.

Find the duration of your video in seconds (e.g., a 2-hour movie = 7200 seconds).
The Formula:
(TargetSizeInBits/DurationInSeconds)=TotalBitrate
To be safe (under 4GB), target 3800MB.

The "Safe Under 4GB" Command

Let's say your video is 60 minutes (3600 seconds) long. To hit ~3.8GB, your bitrate should be about 8500k.

Run these two commands in order:

Pass 1 (The Analysis):

PowerShell

ffmpeg -y -i input.mp4 -c:v libx265 -b:v 8500k -x265-params pass=1 -an -f mp4 NUL

This scans the video and creates a log file. NUL tells Windows not to save a video file yet.

Pass 2 (The Real Render):

PowerShell

ffmpeg -i input.mp4 -c:v libx265 -b:v 8500k -x265-params pass=2 -c:a aac -b:a 128k output.mp4

This uses the log from Pass 1 to distribute the bits perfectly so you don't go over your size limit.

Wait, how do I find the Bitrate for my specific video?

Since you're a geek, don't do the math manually. Use this PowerShell one-liner to calculate the exact bitrate needed to hit 3900MB (giving you a 100MB safety buffer):

PowerShell

$sec = (ffprobe -v error -show_entries format=duration -of default=noprint_wrappers=1:nokey=1 "input.mp4"); $bitrate = [math]::Floor((3900 * 8192) / $sec - 128); echo "Use Bitrate: ${bitrate}k"

Why use Pass 2 instead of just CRF?

CRF (Constant Rate Factor): You're guessing. You might set it to 28 and get a 3GB file, or set it to 22 and get a 5GB file.
Two-Pass: It’s like a "Budget Manager." It looks at the whole movie, sees where the action scenes are, and makes sure the total file size lands exactly where you requested.