Search This Blog

Showing posts with label Win11. Show all posts
Showing posts with label Win11. Show all posts

Sunday, January 14, 2024

Windows 11: Change boot logo follow-up

Fix for missing A: drive during HackBGRT image replacement

This post is a follow-up for the original post that I made, that you can find here. I had just downloaded HackBGRT again after the computer had been trying out different OS:es and had a complete reformatting of the harddrive. This time the changing of the boot logo would not work because I experienced issues during the replacement of the image itself.

When the cmd window that HackBGRT opens up you eventually should be able to see the A: drive using the file explorer from Paints "open file" function. On my computer this time the A: drive would not show up. This post is simply a quick description of how I could work around it.

1. First I ran the script like normal, but I couldn't find the A: drive so I just saved the image over the default image that HackBGRT comes with. Then I exited the script and rebooted, it had at least updated the attached image but not my image. This means that the script is working.

2. I saved my image in a location that was easy to access.

3. Open PowerShell as admin and entered the following commands:
diskpart
sel disk 0
list part
sel part 0 (or whatever number corresponds to your EFI drive)
assign letter=A
exit

4. Still in admin PowerShell I entered the following code to copy the image and overwrite the one in A:
Copy-Item -Path C:\temp\splash.bmp -Destination A:\EFI\HackBGRT\ -Force

5. Reboot the computer and see if the logo has changed.

Thursday, January 19, 2023

Windows 11: Unsupported Hardware

One of the challenges when installing Windows 11 is meeting the hardware requirements, the download itself is quite easy.

Installing Windows 11 comes with requirements such as having a compliant CPU, having secure boot and TPM 2.0.

There are many ways in which you could bypass these if you run so called unsupported hardware.

In my case the computer didn't meet any of the requirements mentioned above, but the saving grace is perhaps a good amount of storage and an i7 processor. Things could be worse I guess. 

After trying some registry modifications I was close to giving up, but eventually I found a way that worked. My HP Elitebook 2540p managed to get Windows 11 installed, despite 4GB of ram it is running surprisingly well. Even the battery life seems to have gotten better.

So this is how I installed Windows 11 on my 2540p:
 
First download the English International version of the ISO here.
 
I made sure I had downloaded the latest Rufus software to create my USB and I used a USB-drive with at least 32GB of storage. 

In Rufus I then had the option to bypass TPM check and the like, so I used these options to ignore the requirements that kept me from just installing the regular Windows 11 ISO.

After flashing the drive with the modified ISO I could then install it on my PC the usual way, but I had to activate UEFI. After that I only had to configure Windows the usual way.

Using a legit Windows activation key I was then able to use the computer normally and even perform Windows Updates. There wasn't really any bugs and only some niche settings were locked due to the old age of the computer. To some degree I even experienced better user experience with Win11 than Win10.

Wednesday, November 16, 2022

Windows: Maintenance and debloating

Keeping your computer clean on the outside is a good thing, equally important is cleaning up the computer internally as well using software. You might simply not want to go through the steps necessary to reinstall the entire computer so here I list some good commands that you can run in PowerShell as an admin. You can also check my other blog post for some tips and tricks on what you can delete to save space.
 

Commands to run in PowerShell

Run system file checker, this sometimes finds and fixes corrupt system files:
SFC /Scannow

Run the tool for Deployment Image Servicing and Management. Basically these are three levels, the last does a bit of repairing. Run SFC before you run any of the DISM commands:
Dism /online /cleanup-image /checkhealth

Dism /online /cleanup-image /scanhealth

Dism /online /cleanup-image /restorehealth

This command can help you recalibrate your system clock. I found it helpful when syncing the clock on computers with a bad battery when internet access have been stopped either by a VPN or because the web browser notices an all too big of a time change. 
Simply run this command to fix the clock:

W32tm /resync /force

In order to fix basic network issues you can run the following commands in this order, the second will disconnect your from the internet usually.

Ipconfig /flushdns

Ipconfig /release

Ipconfig /renew

When changes have been made to the group policy you can try this command to force an update. Pay attention to what settings that override which as well so that you aren't waiting for an update that might not show up.

Gpupdate /force

Running this command let's you check the health of your harddisk.
Chkdsk /f

This command will help you to scan your memory for issues (this command is a program that you can call upon):
mdsched.exe

Some programs to run

Apart from these commands that you can run as admin in the PowerShell window, there are a few built-in programs that you find by searching in your start menu. These are just a good habit to run once in a while to do some cleaning:

Disk cleanup
Disk defragmentation
Storage settings (it will list items you can delete as well)
Full Windows virus scan
 

Debloating script

I've also put together a script that runs through basic pre-installed software and removes it. Sometimes I've tried removing every AppxPackage that I could find, but I found things to get a bit buggy. So this script contains apps that you can live without, all in the name of more resources to what you think is important.

# Run as admin

# Silence errors
$ErrorActionPreference = 'SilentlyContinue';

# App list
$applist = "*3dbuilder*","*windowsalarms*","*windowscommunicationsapps*","*windowscamera*",
"*officehub*","*skypeapp*","*getstarted*","*zunemusic*","*windowsmaps*","*solitairecollection*",
"*bingfinance*","*zunevideo*","*bingnews*","*onenote*","*people*","*bingsports*","*soundrecorder*",
"*bingweather*","*xboxapp*","*xbox*","*Microsoft.MixedReality.Portal*","*GetHelp*","*Microsoft.Messaging*",
"*sketch*","*sticky*","*phone*","*sticky*","*photos*","*calc*","*gethelp*","*camera*"

foreach ($app in $applist) {Get-AppxPackage $app | Remove-AppxPackage}
 
The script works by creating a list where every item is a search word related to apps that can be installed in Windows. If it doesn't find the app it will continue to the next object. When it finds an object it passes it through the pipeline to the removal cmdlet.