Restructured Documentation
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 8s

This commit is contained in:
2026-09-05 14:08:43 -06:00
parent c4bd235eba
commit 289769a601
281 changed files with 5403 additions and 3563 deletions
@@ -0,0 +1,26 @@
---
tags:
- Windows and Linux
- Restrict Monitors on Plasma Login Screen
---
## Purpose
I wrote this document because CachyOS's desktop environment has this dumb issue where the login screen tries presenting itself on every monitor, and due to my unique configuration that includes an invisible display created from my soundbar, I have to run the commands below to configure the Plasma login screen to mimic my environment.
### Configure the Displays
The first thing you want to do is configure the displays so they are arranged / cloned the way you want. This will be mirrored into the login screen configuration.
### Copy Display Configuration into Plasma Login Screen
Run the following commands as your normal user, do not run them as `root`.
```sh
sudo install -d -o plasmalogin -g plasmalogin /var/lib/plasmalogin/.config
sudo cp ~/.config/kwinoutputconfig.json /var/lib/plasmalogin/.config/kwinoutputconfig.json
sudo chown plasmalogin:plasmalogin /var/lib/plasmalogin/.config/kwinoutputconfig.json
```
### Logout and Verify
At this point, the lock screen / login screen should be correctly configured to mirror the normal desktop environment and display arrangement.
## Related Documentation
- [Related Windows and Linux Documentation](<../../../../reference/Windows and Linux/index.md>) — Find the connected deployments, procedures, and references for this subject.
@@ -0,0 +1,24 @@
---
tags:
- Fedora
- Linux
- Flatpak
- Workstation
---
## Purpose
You may need to install flatpak packages like Signal in your workstation environment. If you need to do this, you only need to run a few commands.
```sh
# Usually already installed
sudo dnf install flatpak
# Add Flathub Repo
flatpak --user remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
# Install Signal
flatpak install flathub org.signal.Signal
```
## Related Documentation
- [Related Windows and Linux Documentation](<../../../../reference/Windows and Linux/index.md>) — Find the connected deployments, procedures, and references for this subject.
@@ -0,0 +1,21 @@
---
tags:
- Fedora
- Linux
- Workstation
---
## Purpose
If you want to upgrade Fedora Workstation to a new version (e.g. 41 --> 42) you can run the following commands to do so. The overall process is fairly straightforward and requires a reboot.
```sh
sudo dnf upgrade --refresh
sudo dnf system-upgrade download --releasever=43
sudo dnf system-upgrade reboot
```
**Additional Documentation**:
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-release/
## Related Documentation
- [Related Windows and Linux Documentation](<../../../../reference/Windows and Linux/index.md>) — Find the connected deployments, procedures, and references for this subject.
@@ -0,0 +1,18 @@
---
tags:
- Linux
- Bash
- Scripting
---
## Purpose
This document records the procedure for repair displaylink usb authorization. Follow the environment assumptions and commands below.
```sh
xrandr --auto
xrandr --setprovideroutputsource 4 0
xrandr --output HDMI-1 --primary --mode 1920x1080 --rate 75.00 --output DVI-I-1-1 --mode 1920x1080 --rate 60.00 --right-of HDMI-1 --output -eDP-1 --off
```
## Related Documentation
- [Related Windows and Linux Documentation](<../../../reference/Windows and Linux/index.md>) — Find the connected deployments, procedures, and references for this subject.
@@ -0,0 +1,76 @@
---
tags:
- Windows
- Windows and Linux
---
## Purpose
Record the commands and generic installation-key reference used to change a Windows edition. Select the command and edition that match the target operating system.
### Changing Editions
Windows Server: `DISM /ONLINE /set-edition:serverstandard /productkey:AAAAA-BBBBB-CCCCC-DDDDD-EEEEE /AcceptEula`
Windows (Home/Pro): `DISM /ONLINE /set-edition:professional /productkey:AAAAA-BBBBB-CCCCC-DDDDD-EEEEE /AcceptEula`
### Force Activation / Edition Switcher
`irm https://get.activated.win | iex`
## Generic Install Keys
### Windows 10
| Windows Edition | RTM Generic Key (Retail) | [**KMS Client Setup Key**](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612867(v%3dws.11)) |
| :--- | :--- | :--- |
| Windows 10 Home | YTMG3-N6DKC-DKB77-7M9GH-8HVX7 | TX9XD-98N7V-6WMQ6-BX7FG-H8Q99 |
| Windows 10 Home N | 4CPRK-NM3K3-X6XXQ-RXX86-WXCHW | 3KHY7-WNT83-DGQKR-F7HPR-844BM |
| Windows 10 Home Single Language | BT79Q-G7N6G-PGBYW-4YWX6-6F4BT | 7HNRX-D7KGG-3K4RQ-4WPJ4-YTDFH |
| Windows 10 Pro | VK7JG-NPHTM-C97JM-9MPGT-3V66T | W269N-WFGWX-YVC9B-4J6C9-T83GX |
| Windows 10 Pro N | 2B87N-8KFHP-DKV6R-Y2C8J-PKCKT | MH37W-N47XK-V7XM9-C7227-GCQG9 |
| Windows 10 Pro for Workstations | DXG7C-N36C4-C4HTG-X4T3X-2YV77 | NRG8B-VKK3Q-CXVCJ-9G2XF-6Q84J |
| Windows 10 Pro N for Workstations | WYPNQ-8C467-V2W6J-TX4WX-WT2RQ | 9FNHH-K3HBT-3W4TD-6383H-6XYWF |
| Windows 10 S | 3NF4D-GF9GY-63VKH-QRC3V-7QW8P | |
| Windows 10 Education | YNMGQ-8RYV3-4PGQ3-C8XTP-7CFBY | NW6C2-QMPVW-D7KKK-3GKT6-VCFB2 |
| Windows 10 Education N | 84NGF-MHBT6-FXBX8-QWJK7-DRR8H | 2WH4N-8QGBV-H22JP-CT43Q-MDWWJ |
| Windows 10 Pro Education | 8PTT6-RNW4C-6V7J2-C2D3X-MHBPB | 6TP4R-GNPTD-KYYHQ-7B7DP-J447Y |
| Windows 10 Pro Education N | GJTYN-HDMQY-FRR76-HVGC7-QPF8P | YVWGF-BXNMC-HTQYQ-CPQ99-66QFC |
| Windows 10 Enterprise | XGVPP-NMH47-7TTHJ-W3FW7-8HV2C | NPPR9-FWDCX-D2C8J-H872K-2YT43 |
| Windows 10 Enterprise G | | YYVX9-NTFWV-6MDM3-9PT4T-4M68B |
| Windows 10 Enterprise G N | FW7NV-4T673-HF4VX-9X4MM-B4H4T | 44RPN-FTY23-9VTTB-MP9BX-T84FV |
| Windows 10 Enterprise N | WGGHN-J84D6-QYCPR-T7PJ7-X766F | DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4 |
| Windows 10 Enterprise S | NK96Y-D9CD8-W44CQ-R8YTK-DYJWX | FWN7H-PF93Q-4GGP8-M8RF3-MDWWW |
| Windows 10 Enterprise 2015 LTSB | | WNMTR-4C88C-JK8YV-HQ7T2-76DF9 |
| Windows 10 Enterprise 2015 LTSB N | | 2F77B-TNFGY-69QQF-B8YKP-D69TJ |
| Windows 10 Enterprise LTSB 2016 | | DCPHK-NFMTC-H88MJ-PFHPY-QJ4BJ |
| Windows 10 Enterprise N LTSB 2016 | RW7WN-FMT44-KRGBK-G44WK-QV7YK | QFFDN-GRT3P-VKWWX-X7T3R-8B639 |
| Windows 10 Enterprise LTSC 2019 | | M7XTQ-FN8P6-TTKYV-9D4CC-J462D |
| Windows 10 Enterprise N LTSC 2019 | | 92NFX-8DJQP-P6BBQ-THF9C-7CG2H |
| Windows 10 Home | 37GNV-YCQVD-38XP9-T848R-FC2HD | | |
| Windows 10 Home N | 33CY4-NPKCC-V98JP-42G8W-VH636 | | |
| Windows 10 Pro | NF6HC-QH89W-F8WYV-WWXV4-WFG6P | | |
| Windows 10 Pro N | NH7W7-BMC3R-4W9XT-94B6D-TCQG3 | | |
| Windows 10 SL | NTRHT-XTHTG-GBWCG-4MTMP-HH64C | | |
| Windows 10 CHN SL | 7B6NC-V3438-TRQG7-8TCCX-H6DDY | | |
| Windows 10 Home | 46J3N-RY6B3-BJFDY-VBFT9-V22HG | | |
| Windows 10 Home N | PGGM7-N77TC-KVR98-D82KJ-DGPHV | | |
| Windows 10 Pro | RHGJR-N7FVY-Q3B8F-KBQ6V-46YP4 | | |
| Windows 10 Pro N | 2KMWQ-NRH27-DV92J-J9GGT-TJF9R | | |
| Windows 10 SL | GH37Y-TNG7X-PP2TK-CMRMT-D3WV4 | | |
| Windows 10 CHN SL | 68WP7-N2JMW-B676K-WR24Q-9D7YC | | |
### Windows Server
| Windows Edition | RTM Generic Key (Retail) | [**KMS Client Setup Key**](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612867(v%3dws.11)) |
| :--- | :--- | :--- |
| Windows Server 2016 Datacenter | | CB7KF-BWN84-R7R2Y-793K2-8XDDG |
| Windows Server 2016 Standard | | WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY |
| Windows Server 2016 Essentials | | JCKRF-N37P4-C2D82-9YXRT-4M63B |
| Windows Server 2019 Datacenter | | WMDGN-G9PQG-XVVXX-R3X43-63DFG |
| Windows Server 2019 Standard | | N69G4-B89J2-4G8F4-WWYCC-J464C |
| Windows Server 2019 Essentials | | WVDHN-86M7X-466P6-VHXV7-YY726 |
| Windows Server 2022 Standard | | VDYBN-27WPP-V4HQT-9VMD4-VMK7H |
| Windows Server 2022 Datacenter Azure | | NTBV8-9K7Q8-V27C6-M2BTV-KHMXV |
| Windows Server 2022 Datacenter | | WX4NM-KYWYW-QJJR4-XV3QB-6VM33 |
## Additional Reference Documentation
https://www.tenforums.com/tutorials/95922-generic-product-keys-install-windows-10-editions.html
[https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys](https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys)
## Related Documentation
- [Related Windows and Linux Documentation](<../../../reference/Windows and Linux/index.md>) — Find the connected deployments, procedures, and references for this subject.
@@ -0,0 +1,57 @@
---
tags:
- Windows
- Windows and Linux
---
## Purpose
Sometimes you are running a virtual machine and are running out of space, and want to expand the operating system disk. However, there is a recovery partition to-the-right of the operating system partition. When this happens, you have to delete that partition in order to expand the storage space for the operating system.
These commands can be run in a headless environment using just powershell.
!!! warning "Use Correct Drive & Partition Numbers"
In my example codeblock, I assume the OS drive is `0` and the recovery partition is `4`. Please validate your own drive and partition numbers with the supplied `list disk` and `list partition` commands. Failure to identify the correct drive and/or partition could result in the unintended destruction of data.
**From within the VM** > Open a powershell window and run the following commands:
```powershell
diskpart # (1)
list disk # (2)
select disk 0 # (3)
list partition # (4)
select partition 4 # (5)
delete partition override # (6)
select partition 3 # (7)
extend # (8)
exit # (9)
```
1. This opens the disk management CLI tool.
2. This displays all disks attached to the device.
3. Ensure this disk number corresponds to the operating system disk. Open the Disk Management GUI if you are not 100% certain.
4. List all partitions on the previously-selected disk.
5. This partition number is for the partition of type "**Recovery**". If you see a different partition with a type of "**Recovery**" use that partition number instead.
6. This instructs the computer to delete the partition and ignore the fact that it was a recovery partition.
7. You want to select the operating system partition now, so we can expand it. This partition will generally be of a type "**Primary**" and be the largest size partition on the disk.
8. This will expand the operating system partition into the unallocated space that is now available to it.
9. Gracefully close the disk management CLI utility.
## Free Space Validation
From this point, you might want to verify the free space has been accounted for, so you can run the following command to check for free space:
```powershell
Get-Volume | Select-Object DriveLetter, FileSystem, @{Name="FreeSpace(GB)"; Expression={"{0:N2}" -f ($_.SizeRemaining / 1GB)}}, @{Name="TotalSize(GB)"; Expression={"{0:N2}" -f ($_.Size / 1GB)}}
```
!!! example "Output Example"
```text
DriveLetter FileSystem FreeSpace(GB) TotalSize(GB)
----------- ---------- ------------- -------------
C NTFS 398.40 476.20
FAT32 0.06 0.09
NTFS 0.11 0.63
```
## Related Documentation
- [Related Windows and Linux Documentation](<../../../reference/Windows and Linux/index.md>) — Find the connected deployments, procedures, and references for this subject.
@@ -0,0 +1,52 @@
---
tags:
- Windows and Linux
- Uninstall Updates via DISM
---
## Purpose
You may find that you have a machine that does not want to boot because of a recent Windows Update. In these cases, you only viable option sometimes may be to simply uninstall the update. You can do this via a bootable Windows installer (ISO or USB), or you can try to use the built-in recovery menu in windows.
!!! info "Triggering Recovery Menu"
Microsoft's own guidance is a little upsetting, because to trigger the recovery menu to appear, you generally have to let the device reach the Windows splash screen and forcefully shutdown / restart the device 3 times before it triggers. At the time of writing this, I am not aware of any other ways to trigger the menu to appear.
You can circumvent this annoying workflow by simply booting from a windows installer ISO / USB and choosing "**Repair this PC**"
### Recovery Menu Navigation
At this point, you will be presented with a blue menu with large buttons, and one of them will say "**Troubleshoot**" or "**Advanced**", from there, you should see an option for "**Command Prompt**".
### DISM Package Management
At this point, we need to query all of the Windows Updates that have been installed on the device, so we know what to look for to uninstall.
```powershell
# (Low Effort) Determine the Drive Letter of the Offline OS
bcdedit | find "osdevice"
# (Moderate Effort) Determine the Drive Letter via DISKPART
diskpart
list vol
exit
# If the offline OS volume can be identified but lacks a drive letter, assign it one. (e.g. D)
diskpart
list vol
select vol <n>
assign letter=D
exit
# List all Installed Packages (Oldest at Top / Newest at Bottom)
DISM /Image:D:\ /Get-Packages /Format:Table
# Uninstall Packages (Examples Given)
DISM /Image:D:\ /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.4773.1.11
DISM /Image:D:\ /Remove-Package /PackageName:Package_for_ServicingStack_4763~31bf3856ad364e35~amd64~~20348.4763.1.2
```
### Reboot and Validate
At this point, you should be safe to close the command prompt and attempt to reboot the computer. If it still doesn't boot, you can try alternative offline repair methods such as `DISM /Image:D:\ /Cleanup-Image /RestoreHealth` and `sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows`. If you have an install ISO mounted / accessible to the problematic device, you can tell DISM to exclusively use that install media to repair the OS:
- `DISM /Image:D:\ /Cleanup-Image /RestoreHealth /Source:wim:X:\sources\install.wim:1 /LimitAccess`
- `DISM /Image:D:\ /Cleanup-Image /RestoreHealth /Source:esd:X:\sources\install.esd:1 /LimitAccess`
## Related Documentation
- [Related Windows and Linux Documentation](<../../../reference/Windows and Linux/index.md>) — Find the connected deployments, procedures, and references for this subject.
@@ -0,0 +1,42 @@
---
tags:
- Windows
- VSS
- Backup
---
## Purpose
There are times when you may need to delete shadow copies (Volume Shadow Copies) from a drive, commonly to free up disk space. While this is usually straightforward, you may encounter scenarios where shadow copies cannot be deleted through normal means. The following methods provide ways to forcibly remove all shadow copies from a specific volume.
!!! warning
The examples below will **permanently delete all shadow copies** on the specified drive. The examples use drive `D:` > Adjust the drive letter as needed.
## Method 1: Delete Shadow Copies Using `vssadmin`
The `vssadmin` utility is the standard tool for managing shadow copies. It is typically safe and handles deletions gracefully.
However, some antivirus or endpoint protection software may block its execution due to its similarity to behavior used by ransomware. If `vssadmin` fails, use the `diskshadow` method described below.
```cmd
vssadmin delete shadows /for=D: /all /quiet
```
- `/for=D:` specifies the target volume.
- `/all` removes all shadow copies on that volume.
- `/quiet` suppresses confirmation prompts.
## Method 2: Delete Shadow Copies Using `diskshadow`
`diskshadow` is a more direct and lower-level tool than `vssadmin`. It should be used as a fallback option if `vssadmin` fails or is blocked.
```cmd
diskshadow
set context persistent nowriters
delete shadows volume D:
exit
```
Explanation:
- `set context persistent nowriters` ensures the command does not involve writer components (e.g., for backups), reducing the chance of interference.
- `delete shadows volume D:` removes all persistent shadow copies for volume `D:`.
## Related Documentation
- [Related Windows and Linux Documentation](<../../../../reference/Windows and Linux/index.md>) — Find the connected deployments, procedures, and references for this subject.
@@ -0,0 +1,25 @@
---
tags:
- Windows 11
- Windows
- User Accounts
---
## Purpose
You may find that Windows 11 does not allow you to install it with a local account. This is a documented case of Microsoft attempting to push Microsoft accounts, and can be bypassed by following the workflow below:
## Initial Boot to Windows 11 Installer
- Begin installing the OS as normal, selecting the region/language
- Before you accept the EULA, press `SHIFT+F10` to open the Administrative Command Prompt
- ~Type `OOBE\BYPASSNRO` > This will reboot the computer back into the installer~
- The `OOBE\BYPASSNRO` method no longer works, instead type the command `start ms-cxh:localonly`, you will then be prompted to enter a local user account and the OOBE will finalize.
## Second Boot to Windows 11 Installer
- When prompted for an internet connection, select `I don't have Internet`
- Set up the local administrator account as normal and finish the OS installation process
!!! warning "Disconnect Internet"
To ensure a clean installation devoid of additional issues, make sure to disconnect the physical/virtual network from the device before proceeding to install Windows 11 as normal. This time, you will not be prompted to login with a Microsoft account.
## Related Documentation
- [Related Windows and Linux Documentation](<../../../../reference/Windows and Linux/index.md>) — Find the connected deployments, procedures, and references for this subject.
+17
View File
@@ -0,0 +1,17 @@
---
tags:
- Windows and Linux
- Workflows
- Documentation
---
# Windows and Linux
## Purpose
Find workflows for windows and linux. Follow the subject guide to choose the relevant environment and connect this material to the other document types.
## Includes
- Linux
- Windows
## Follow the Subject
[Windows and Linux](<../../reference/Windows and Linux/index.md>) explains the relationships and offers starting points for the documented tasks.