Showing posts with label Windows 10. Show all posts
Showing posts with label Windows 10. Show all posts

Thursday, February 12, 2026

Windows VM notes.

 Despite how much you dislike Windows, especially Windows 11, there are still times which you can't escape from it.  Like many people, I have a virtualbox VM for it, and here are few things I would do to make it "better".

 1) Debloating.  It is not a secret Windows 11 is not lean even with a fresh installed.  Especially if you are unfrotunately having the joy of using its Home edition.  So, the first thing you may want to do is to trim it down.  Win11Debloat may be a good start.

 https://github.com/Raphire/Win11Debloat

 

 

 

 



2) Compact the VDI image. There are times you either just want to keep the VDI file size in control or you want to export the VM as OVA for backup. For both instance, you may want o compact your VDI first. Here are steps I would take.

a) run Windows' Cleaner tool to delete any obsolete/residue files left from Windows updates.

b) run sdelete to "zero" the empty spaces after the deletion in (a)

sdelete c: /z
sdelete is a power toy tool that can be obtained at: https://learn.microsoft.com/en-us/sysinternals/downloads/sdelete

c) run the Windows defrag tool to defragment the drive, so all empty spaces are in continuous blockss.

d) optional. I often run the (b) again, to zero the empty space once more before the compacting.

e) shutdown the VM, and run the below command on the host machine to the VDI file to compact the file.

 vboxmanage modifyhd <your vdi file> --compact 

 If you get the erorr below, try switch to cmd and try again.

  


 

Friday, August 7, 2015

I have an old Broadcom NetXtreme Gigabit Ethernet NIC, and it worked well with Windows 8.1 but not with Windows 10 (at least not with the version I had).

Anyway, today I managed to find a set of drivers which work. The driver I found is from Lenovo for its THINKSTATION S10 (TYPE 6423, 6483), ver. 10.86.0.0.  Its URL is:
http://support.lenovo.com/us/en/downloads/ds000638

If you are having one of these Braodcom NIC below, you may want to give it try.

5700, 5701, 5702, 5703, 5704, 5705, 5751, 5753, 5754, 5755, 5756, 5782, 5786, 5787, 5788, 5789, 5901, 5906


By the way, the hardware ID for my card is:

PCI\VEN_14E4&DEV_16A6



Wednesday, August 5, 2015

Change Window 8/10 Network Location using PowerShell

One thing that I am really annoyed by Windows 8 and then now Windows 10 is Set/Change network location.  Microsoft manages to make something so easy in Windows 7 to something that is so convoluted in new versions.

If you are comfortable with using commands, you may want to use PowerShell to change the Network Location instead.

1) You need to start PowerShell with elevated user account with command as below.
PSH>Start-Process WindowsPowerShell.exe -verb RunAs
Alternatively, you can type powershell in Search, and run it as an administrator by using the "Run As" option from the context menu (right click)

2) Use the Get-NetconnectionProfile to find out the InterfaceIndex of the connected NIC, e.g.
PSH> Get-NetConnectionProfile
......
Name : Unidentified network
InterfaceAlias : vEthernet (Local-10)
InterfaceIndex : 18
NetworkCategory : Public
IPv4Connectivity : LocalNetwork
IPv6Connectivity : LocalNetwork

3) Use the Set-NetConnectionProfile to change to the desired network location.
PSH> Set-NetConnectionProfile -InterfaceIndex 18 -NetworkCategory Private
That's it. This saves you from switching account, and then jump through hoops to get the network location changed.

(ref: http://blogs.msmvps.com/russel/2013/12/29/set-network-location-to-private-in-windows-8-1server-2012-r2/)