Basically, the display is cut off! So if I were trying to install a new OS, it wouldn’t be very efficient since I’d have to guess what was on display; e.g.
As it turns out, using the correct search phrase returns the answer. HINT: it’s a compatibility issue between the client and display scaling in Windows 10; e.g. mine was set to 150%.
TLDR: The solution is to set display scaling to 100%, and then log out and in for the changes to take effect.
… but hey, better late than never!
So I was just complaining about how PuTTY doesn’t seem to handle SSH keys (e.g. AWS, Azure) very well, and then I came to (belated) realization that because rsync can be used in Windows via Cygwin, so can ssh.
Now I don’t waste time in a UI managing PuTTY profiles, generating PPKs, or fidding with regedit.exe to clean up cached host fingerprints.
Try Cygwin, today.
A keylogger records when a key is pressed, when it is released, and whether any shift or special keys have been pressed. It is also recorded if, for example, a password is entered even if it is not displayed on the screen.
There is no evidence that this keylogger has been intentionally implemented. Obviously, it is a negligence of the developers – which makes the software no less harmful. If the developer would just disable all logging, using debug-logs only in the development environment, there wouldn’t be problems with the confidentiality of the data of any user.
I found the file MicTray64.exe in my HP EliteBook 840 G3. It’s barely 2 months old, running an up-to-date version of Windows 10 Pro. The prudent measure was to remove this file, as neither Conexant nor Hewlett-Packard hasn’t deigned to respond. I was unable to find the log file C:\Users\Public\MicTray.log, though.
I quickly pressed Windows Key + q to open the Search box and typed in: turn windows features on or off Turn windows features on or off I scanned a few options but one in particular was salient: Hyper-V was enabled.
So I installed the 64-bit version of Docker for Windows after configuring a shiny new VirtualBox CentOS 7 guest. The latter’d ran just fine previously, but was now causing a BSOD, and I wasn’t even able to create new 64-bit guests.
As it turns out, installing Docker enables Hyper-V, but uninstalling Docker doesn’t disable Hyper-V; i.e. these virtualization technologies are incompatible. The fix to this is quoted above: disable Hyper-V.
Fixing this issue is pretty straightforward and involves a few simple steps.
- Load up task manager (right click taskbar and select Task Manager)
- Go to the Processes Tab
- Select rdpclip.exe
- Click End Process
- Go to the Application Tab
- Click New Process
- Type rdpclip
- Click Ok
Updated for Windows 10.
I noticed that with the power turned off at boot time, I’d be unable to adjust my screen brightness. Instead of the usual 3 options (Turn off the display, Put the computer to sleep, and Adjust plan brightness), just 2 were available; i.e. Adjust plan brightness” had disappeared!
This is probably due to a bad driver (e.g. TeamViewer). The workaround is to restart Windows with the power plugged in, but this is a bothersome fix.
A better solution is to hit Windows + x: Device Manager: Monitors: (Select your monitor): Properties: Driver: Uninstall.
Post-uninstall, click Action: Scan for hardware changes. Your monitor should reappear, this time with the good driver installed.