If you’re trying to run compmgmt.msc (Computer Management) or any other MMC snap-in via the runas command, you might’ve seen Error 193: compmgmt.msc is not a valid Win32 application. This is simply due to some complications with the runas command. If you just type compmgmt.msc without runas, it’ll open successfully. The reason is some complications with the runas command.
Luckily there’s an easy solution. Since compmgmt.msc is not a regular win32 (or a typical exe) application, you have to prepend “mmc” in order to tell Microsoft that you’re trying to run a Microsoft Management Console snap-in.
runas /user:domain\username "mmc compmgmt.msc"
This is also the case for every other *.msc snap-in, such as lusrmgr.msc.
I’ve mentioned this briefly in an earlier post as well:
First of a quick clarification regarding Windows licenses.
An OEM Windows license are bundled with prebuilt computers from hardware manufacturers (like Dell and Asus). These keys are only valid for that specific computer. An OEM key can not be used on any other computers, even if you extract the license key.
A Retail Windows license works similarly that it will only work on 1 computer, but you can choose which computer to use it on and reassign it to another computer if you’d like to.
To sum it up; an OEM key belongs to the computer while a retail key belongs to you.
Now there are still valid reasons to extract the OEM license key and that’s what we’re going to do today. The OEM key for Windows 8, 8.1 and 10 are now stored in the BIOS/UEFI (using ACPI) and no longer written on physical stickers like it used to.
Easiest method is to use the builtin wmic interface by running this command in command prompt:
wmic path softwarelicensingservice get OA3xOriginalProductKey
Alternatively you can start PowerShell and type get-wmiobject and enter SoftwareLicensingService when it prompts for what Class to use.
Nir Sofer gets the job done as usual. This will also list other used license keys, not just the operating system. See example screenshot below, but note that my hardware has been modified and therefore has no OEM key.
This is a very powerful tool which you should use with great caution. This application talks directly with your firmware and since it also can WRITE data in addition to READ, you must be very careful so you don’t break anything. If the other steps above did not work, you can give RWEverything a try. See further instructions from this Stackexchange thread: https://superuser.com/a/593795/312773
I just upgraded from 18.04 to 18.10 yesterday, but to my dismay, the new fancy theme, Yaru, was nowhere to be found. Looked around in Gnome Tweaks to no avail. Turns out some of the theme packages were not properly installed, more specifically the yaru-theme-gtk package.
Enter the command apt search yaru-* to see installation status of every package containing “yaru-*”. If they are installed they will state [Installed] inside the square brackets, like so:
If they’re not installed, you can simply fix the issue by running sudo apt install yaru-*. Once complete, log out and back in, and the theme files will be available in Gnome Tweaks.
Voila! Remember to also set Cursor, Icons and Sound theme to Yaru in Gnome Tweaks if desired.
If your computer still requires you to press CTRL ALT DEL upon login, this simple guide will teach you how to disable it. Note that this will require administrator access and it might not work on Windows Home editions as it requires to modify local group policies.
Browse to Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options
Locate the policy called “Interactive logon: Do not require CTRL+ALT+DEL“
Doubleclick the policy and set it to Enabled
Starting from your next restart, you should no longer be required to press CTRL+ALT+DEL at the Windows login prompt.
If you’re running on older Windows version the policy might be called “Disable CTRL+ALT+DEL requirement for logon”
I just had to install some old legacy software on a new Windows 10 computer. Vendor says it “should work”, but apparantly not without some challenges.
Fast forward ten minutes. Application installed successfully. A couple dll error messages during the setup but I happily ignored those and went on my way.
I cross my fingers and start the application…. nothing happens. Try again. Reboot. Still nothing. Login as local administrator account and reinstall software. Nothing. Start in compatibility mode for XP and set to 256 colors… nothing. Run as admin. Nothing works, you know the drill.
So naturally our next point is to either give up or go all in and fire up ProcessMonitor. Unfortunately we really needed this to work so ProcMon it is.
1) First of we have to set up some filters. Click on the Filter button as showed in the picture below:
2) Set the Process Name == executable filename.exe and Result != SUCCESS. Leave the default filters as they are.
3) Now clear the log for good measure and start the troubling application. ProcMon will now be populated with every single failed event processed by the application.
In the picture above I started to notice a pattern with .NET framework. Then I remembered we had some other software which required .NET framework 3.5, and that’s not easily available on Windows 10. So the next thing I did was to install .NET framework 3.5 and the application worked!!
See this other post for .NET 3.5 install instructions: