Skip to content

Latest commit

 

History

6 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 

Repository files navigation

Screenshot 2025-05-05 235141 Screenshot 2025-05-06 002041 Screenshot 2025-05-06 001940 Screenshot_06-May_04-13-24_4866


⚙️ Step-by-Step Configuration Process from windows configuration.docx


Step 1: Clone Windots Repository

Command:

git clone https://github.com/RohitRai1141/MyWindowsConfig.git

✅ No error encountered.


Step 2: Navigate into Windots directory

Command:

cd windots

✅ No error encountered.


Step 3: Run setup script

Command:

.\setup.ps1

Error:

.\setup.ps1 : File C:\Users\[user]\windots\setup.ps1 cannot be loaded because running scripts is disabled on this system.

👉 Go to Step 4 to fix the error.


Step 4: Enable Script Execution

Command:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

✅ Fixes script execution issue.


Step 5: Re-run the setup script

Command:

.\setup.ps1

Error:

No match was found for the specified search criteria and module name 'WinGet'. Try Get-PSRepository to see all available registered module repositories.

👉 Go to Step 6 to fix the error.


Step 6: Enable TLS 1.2 to fix WinGet/PowerShell errors

Command:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

✅ Fixes the TLS error that blocks module installation.


Step 7: Re-run the setup again

Command:

.\setup.ps1

✅ This time it proceeds without error and begins installing dependencies and symlinking config files.


Step 8: Restart the machine

✅ Restarted as required after the configuration completed.


Step 9: Open GlazeWM and check terminal layout

Command:

winfetch

Error:

winfetch : The term 'winfetch' is not recognized as the name of a cmdlet...

👉 Go to Step 10 to fix winfetch not found issue.


Step 10: Install Winfetch manually

Command:

winget install Winfetch

✅ Winfetch installed manually after the setup script failed to handle it.


Step 11: Re-run winfetch

Command:

winfetch

✅ Output now shows correctly with system information.


Step 12: Configure fonts manually (due to missing automatic install)

Steps:

  1. Download font from Nerd Fonts
  2. Install fonts manually by double-clicking or dragging into Fonts settings
  3. Apply the font in Windows Terminal settings → Profiles → Defaults → Appearance → Font Face

✅ Font now renders correctly in terminal with proper symbols.


Step 13: Fix config.yaml path in GlazeWM if not loading

Steps:

  1. Go to C:\Users\[username]\AppData\Roaming\glazewm\config.yaml
  2. Confirm it's symlinked to windots/config/glazewm/config.yaml
  3. If broken:
New-Item -ItemType SymbolicLink -Path "C:\Users\[username]\AppData\Roaming\glazewm\config.yaml" -Target "C:\Users\[username]\windots\config\glazewm\config.yaml"

✅ GlazeWM loads the correct config now.


Step 14: Check PowerToys is installed

Observation: PowerToys was not installed automatically.

👉 Go to Step 15 to install manually.


Step 15: Install PowerToys

Command:

winget install Microsoft.PowerToys

✅ PowerToys installed successfully.


Step 16: Launch PowerToys and enable FancyZones

  1. Open PowerToys → FancyZones → Turn on
  2. Set up layout as per preference

✅ FancyZones active and working.


Step 17: Optional – Add PowerToys to Startup (if not auto-starting)

Command:

shell:startup

Drag a shortcut of PowerToys into that folder.

✅ PowerToys now launches on startup.


About

No description, website, or topics provided.

Resources

Stars

2 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors