• Notice regarding image hosts and attachments. See here.

*** Microsoft Windows 11 Thoughts & Discussion Thread ***

Not sure if you can disable nvme in the bios but I'll a look.

If I have to remove the drive it will be a good excuse to deep clean the gpu etc.
As good as NVME drives are they can be a pain when having to remove as a GPU etc can be covering it (GPU covers mine in this system).

I've only ever had 1 drive on my main rig for some time so no need to disconnect any other drives. At least with sata drives you just disconnected the cable so was easily done
 
I just took a chance and formatted both drives through the sandisk software, then installed W11 and re-did all my partitions. Copied data back and going through the slog of installing stuff.
 
Windows-history.webp


Found a way to view current AND historical Windows installs if like me you have done in-place upgrades all this time. The first entry is my original install from Vista, the last entry is the current Windows 11 build. MS changed the logging of how OS versions are logged per install over time. ALso Windows 11 is internally named Windows 10 by MS, annoying.

The PS code:

Code:
& {
    $history = Get-ChildItem -Path 'HKLM:\System\Setup\Source*' -ErrorAction SilentlyContinue | ForEach-Object {
        $props = Get-ItemProperty -Path Registry::$_
        $build = [int]($props.CurrentBuild -replace '[^\d]')
        $product = $props.ProductName
        if ($build -ge 22000 -and $product -like "*Windows 10*") {
            $product = $product -replace 'Windows 10', 'Windows 11'
        }
       
        [PSCustomObject]@{
            ProductName    = $product
            DisplayVersion = $props.DisplayVersion
            CurrentBuild   = $props.CurrentBuild
            InstallDate    = ([DateTime]'1/1/1970').AddSeconds($props.InstallDate).ToLocalTime()
        }
    }

    $curr = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
    $currBuild = [int]($curr.CurrentBuild -replace '[^\d]')
    $currProduct = $curr.ProductName
    if ($currBuild -ge 22000 -and $currProduct -like "*Windows 10*") {
        $currProduct = $currProduct -replace 'Windows 10', 'Windows 11'
    }

    $currDate = if ($curr.InstallTime) {
        [DateTime]::FromFileTime($curr.InstallTime)
    } else {
        ([DateTime]'1/1/1970').AddSeconds($curr.InstallDate).ToLocalTime()
    }

    $currentOS = [PSCustomObject]@{
        ProductName    = $currProduct
        DisplayVersion = $curr.DisplayVersion
        CurrentBuild   = $curr.CurrentBuild
        InstallDate    = $currDate
    }

    $history + $currentOS | Sort-Object InstallDate
} | Format-Table -AutoSize

Edit* Code updated to ignore the MS naming scheme and update Windows 10 to Windows 11 where the build version is actually Windows 11.
 
Last edited:
Was visiting family for two days and loaded up my PC that's there, way slower than this one but still can play Battlefield 6 fine for what it can do. However it said it needed a windows security update. I did that, and when I rebooted the system it was unusuable. It would take around 2 mins just to open anything and the same again to close. I thought maybe it was an app hang, but 1% cpu usage at times with 10% memory usage there was nothing hogging the resources that bad.

Uninstalled the security update, everything back to normal :rolleyes:
 
MS advising people not to install an update... which the end user has no real control over whether it gets installed or not... genius... (though MS has now blocked the update but that is another story).
 
After pausing windows updates for 6 weeks, today I resumed them and a bunch of updates inc the July major one that killed my USB access previously installed. restarted all good. Had a system restore ready to run if it failed but looks like MS fixed whatever it was last time round lol.
 
Hmmm my windows has gone really laggy, opening anything isn't instant... This is what happened to my other PC after a recent windows update.

OH well bed soon lol
 
Noticed something MS removed in the latest features update, when the bin is pinned to the file explorer taskbar pinned context menu, you no longer have the option to empty the bin when right clicking it:

1786096966830.webp


Annoying for me as I now have to open file explorer and right click the bin and empty from the left pane or click on the pinned icon and open the bin then click the empty button.

It has turned a 3 click process into 4 clicks......
 

After roughly 8000 years, Microsoft finally think to do something about one of their worst features, "Microsoft bag warmer™".
This one was incredibly annoying, and the thing that pushed me to installing Mint on to my laptop instead. Getting in to the office every day and pulling out a toasty laptop with no battery took the shine off of the (at the time) new device.
Too busy thinking of ways to harvest user data, instead of making a decent OS.
 
I don't hide my taskbar, but I find it useful and the slight delay in unhiding is annoying. Not scared of 'burn in' either.
 
There is no delay at unhiding if you are using StartAllBack - It instantly shows on mouse hover, or even with stock start and taskbar if you turn of one of the slide animation effects in Windows settings.

1786355084694.webp


The benefit of hiding the task bar is two fold

1: It gives you more viewable screen space when working in apps or browsing as a taskbar isn't taking up the extra pixels.
2: It is reactive anyway, if your open windows don't nudge into the taskbar area, then the taskbar keeps itself visible, as soon as you maximise or move an app window into the taskbar area it auto hides until the area is no longer occupied again.
 
No I CBA installing extra stuff when the default one works fine. I'm using a 42" 4k screen so space isn't an issue :)
 
  • Like
Reactions: TNA


1786481977875.webp
 
Back
Top Bottom