Windows 10 - UEFI - USB Bootable Key - install.wim too big for FAT32 (>4GB)

Hi,
I was trying to prepare a Windows 10 USB bootable setup Key today.
It was for a uefi system, so I formatted the key FAT32 and copied all the files from the DVD but it stopped with an error about install.wim too big for the support (it was >4GB in size).

I found this nice article explaining how to bypass the issue:
https://win10.guru/usb-install-media-with-larger-than-4gb-wim-file/

To make it short:
- delete all partitions from your usb key
- create a 1GB FAT32 partition
- create another partition with the rest of the space and format it NTFS
- copy all the files and folders EXCEPT "sources" folder, from the DVD to the FAT32 partition
- on the FAT32 partition create a "sources" folder and copy the \sources\boot.wim" file in it from dvd
- copy ALL the files and folders from the DVD to the NTFS partition

this key should be able to boot , the windows setup should appear and you should be able to install windows succesfully, at least it worked in my case

obviously, when I write "DVD" it could be also an ISO files mounted on the PC as source of the files

good luck
and thanks to Kari Finn and Martin aka Cereberus

Permanently set and save process Priority

Usually we set the process priority using task manager, the problem is that once the process get restarted you loose the priority set.

You can play with the registry to solve this.

Let's say the process you want to start in LOW priority is "notepad.exe"

this is the registry location to look for (if you don't find the folder names, you need to create them) :

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\notepad.exe\PerfOptions]

And then you need to create these 2 DWORD keys:

"CpuPriorityClass"=dword:00000001

"IoPriority"=dword:00000000

where the values 1 and 0 come from this table:

CpuPriorityClass Value Priority 

1 Idle2 Normal3 High5 Below Normal6 Above Normal 

IoPriority Value Priority 

0 Very Low1 Low2 Normal

thanks to Alois Kraus
source: http://geekswithblogs.net/akraus1/archive/2013/08/14/153728.aspx

W10 - HIGH DPI SCALING FIX BLURRY APPS

On W10 due to high resolution screens, often the user set the screen scaling to better read the texts and icons, for example to 150%

After that, it happens that some app's text appears to be blurry, out of focus.

You can fix this in 3 places:
1. control panel, apply to the system
2. single app
3. registry

1- Using Control Panel, apply to the System
start menu, settings, system, display, here you have "Scale and layout " set for example to "150%",
click the link "Advanced Scaling Settings" and activate the option "Let Windows try to fix apps so they're not blurry"

2-single app
navigate to the executable file of the app (just as an example: c:\program file\blurryapp\blurry.exe" )
right click on the .exe file
"compatibility" tab
"change settings for all users" (if this is what you want)
"change high DPI settings"
select "Override high DPI scaling behavior." option
and then select "Application" in Scaling performed by

3. registry (this is useful for control panel apps , dll run by RUNDLL32.exe and similar)
When the blurry app does not have an executable (like the apps in the control panel for example) you can use the registry.
An example is Microsoft System Configuration Manager. It's window is blurry when scaling is activated.
Proceed like this:

regedit
create this key:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]

then create a STRING value, where the name is the executable path and the value is "HIGHDPIAWARE"

in the RUNDLL32.exe case it's like this (you can copy and paste this into a .reg file, double click it to insert in the registry)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"C:\\Windows\\System32\\rundll32.exe"="HIGHDPIAWARE"

Once the setting is in the registry, simply close and reopen the app and it will be ok, no reboot is needed.

I used HKLM because is the simplest one, it applies to all user profiles of the machine, already existing and new one when they will be created

Windows change keyboard layout in remote desktop always revert to default (eng)

Hi,
if you are experiencing Windows (2016 server in my case) in remote desktop to automatically change the Keyboard Layout to the default (ENG) one, whatever you set , you are in the right place.

In the last days I fought against my Windows 2016 server. I set the keyboard layout to ITA but without apparent reason it automatically revert to ENG anytime .

I tried in many way to fix it, but it always reverted to ENG, also if in the control panel I deleted any keyboard layout and left just the one I wanted.

Solution:

open regedit, navigate here (be careful! Layout  - NOT Layouts )

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout

create this :

 IgnoreRemoteKeyboardLayout   DWORD   1

logout/login (or reboot the machine), the keyboard layout should be now the one selected from you, if the layout is not set to the correct one, set it , then it should not change anymore.

VmWare player / workstation bridged nic does not get IP Address and Virtualbox error : VERR_INTNET_FLT_IF_NOT_FOUND

On a pc where I was able to run virtualbox and vmware player using a bridged NIC , from one point in time on I was not able anymore to make them work.

I tried many of the solutions found in internet but noone was helping me.

In the end what did the job was to uninstall the nic drivers and install the windows default version like this:

1- windows device manager
2- find the NIC you are trying to use with virtualbox
3- check the driver version, maybe you need this in a later step
4- be sure to have somewhere this or other drivers version for this nic in case windows does not have any driver for it and you want to revert to the actual situation
5- uninstall it (and flag the "delete the driver software for this device" also)
6- run "scan for hardware changes"

If you are lucky, windows will detect the nic and install the windows default drivers for it, and in my case this solved the issue, probably the updated drivers I was using (from the vendor) was not compatible with virtualbox.

If you are not lucky, the nic will be detected but drivers not installed, in this case you should try to install a driver different from the one find in the point 3, maybe something older or something newer.
If you don't have any different version, in the worst case, you'll reinstall the same drivers in point 3 but probably you'll not solve your issue, but at least you'll be able to use your network like before, not from the virtual machine, sorry.

I want to know the PATH of an EXE

Never happened that you run an exe from command prompt and you are not sure from what path it's run? sometimes this make the difference. Maybe you have multiple version of an exe, in multiple path or something like that, it's not working like expected and you want to be sure the correct one is run.

If the executable is gui application this is not really an issue, you can obtain the info from the task manager adding for example the "cmd" column, but if the executable is a command line one, that start and end in milliseconds, than you are in trouble.

One clue come from the command "where.exe":

where executablename

will give you all the path where that executable can be find.
But this will not tell you from which path it is run when you digit:

executablename

from a random folder from command prompt

As I'm not aware of any other way to know the path where it is run from , I wrote a very small console application in C# that simply run the process and print the process filename:

si = new ProcessStartInfo(args);
using (Process pr = Process.Start(si))
{
  Console.WriteLine("*****************************************************");
  Console.WriteLine(pr.MainModule.FileName);
  Console.WriteLine("*****************************************************");
}

this does exactly what I need.

For example running my app from a random folder against "dism.exe" I see this:

C:\it>exepath dism

*****************************************************

C:\Windows\System32\Dism.exe

*****************************************************

Vsphere VCENTER Server virtual appliance installation Stuck at 80% (and/or RPM installation failed)

I tried to install an old ISO image of the Vcenter virtual appliance from the 2017 and I discovered it was not installable anymore.

The installation progress stuck at 80% and in the end it failed with RPM installation failed.

Reading around it seems a bug in the image itself, the setup process cannot change the root password and so cannot continue and it fails.

Solution (in my case) :

Simply download the latest VCSA .ISO from VmWare site
(I just installed this succesfully: VMware-VCSA-all-6.5.0-7119157.iso )

NOTE: also this version seems to stuck at 80%, it will take a long time to move from 80% but in the end it will be able to pass it and finish the installation

Digger