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
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”
AFAIK there is no command in Windows to quickly see the uptime. However, there are several commands to get the last boot time, although you’ll have to do a quick calculation if you need the uptime in days. The easiest/fastest method is to use net stats.
Run command: net stats srv
C:\Users\kek>net stats srv
Server Statistics for \\hostname
Statistics since 09.11.2017 00.02.28 # last boot/uptime
Sessions accepted 1
Sessions timed-out 0
Sessions errored-out 0
Kilobytes sent 1649
Kilobytes received 1181193
Mean response time (msec) 0
System errors 0
Permission violations 0
Password violations 0
Files accessed 329
Communication devices accessed 0
Print jobs spooled 0
Times buffers exhausted
Big buffers 0
Request buffers 0
The command completed successfully.
If you’re trying to install .NET Framework 3.5 using the regular installer, it’ll most likely say you already have a newer version installed. Luckily you can still install it using some other methods which I’ll quickly go through today along with its probability of success (because for reasons they only work sometimes).
Using Windows Features – probably won’t work
Open appwiz.cpl (Programs and Features) and click on Turn Windows features on or off 
Mark the checkbox for .NET Framework 3.5 (includes .NET 2.0 and 3.0)
Using DISM online version – might work
Open command prompt as administrator
Enter command: DISM.EXE /Online /Add-Capability /CapabilityName:NetFx3~~~~
If it works you’ll see a progress bar for the download + installation.
Using DISM offline version – works most of the time
Get a copy of the .NET Framework 3.5 installation .cab file.
You can find this inside the Windows 10 install .iso file (open the .iso file in 7-Zip or any other package utility and copy the microsoft-windows-netfx3-ondemand-package.cab file from \sources\sxs\ directory to a place on your drive, like C:\Temp
Enter command: DISM.EXE /Online /Add-Package /PackagePath:C:\Temp\microsoft-windows-netfx3-ondemand-package.cab
If it works you’ll see a progress bar for the installation.
There are many ways to manage your Internet Explorer passwords. The tricks below should also work for newer Windows versions as well.
1) Use registry to export the entries
Open regedit and browse to Computer\HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\IntelliForms\SPW. You will see a list of encrypted password entries in the right column. Click on File -> Export to save the contents to a .reg file. Proceed to import this on your new PC.
2) Use the Windows Credentials Manager
Open Control Panel and go to User Accounts -> Credential Manager.
Your IE saved passwords will be available in the Web Credentials tab.
3) Export/import with credwiz.exe utility
Open the Run prompt by pressing [WIN]+[R] buttons, type credwiz.exe and press the ENTER key.