So you got the Windows 10 update of December 2017 and now your keyboard num lock, caps lock and scroll lock lights (LED) no longer work.
Check windows version as this fix worked for me on this version
open a command prompt by typing ‘cmd’ into the search bar then enter
you should see something like
IF your version is even close this should work fine.
Open Device Manager, and goto ‘Universal Serial Bus controllers’. Start removing ‘USB Root Hub’ devices until your keyboard stops working.
Give it a few seconds, then restart your computer.
All Done. Enjoy
Well… It landed. Windows 10 Creators Update.
As promised the install did reboot several times and took almost 10 minutes on a SSD drive. Could be a painful update if your system drive is a hard disk.
Open a command prompt and you should be looking at:
Version 1703 (OS Build 15063.138)
Now to check the Bash.
If you are stuck for decent free UPS monitor and graceful shutdown software for Windows 10, or a bit put out by the lack of software or enormous Java apps provided by many UPS manufacturers, you can’t do much better than these two apps.
It does depend on your UPS as to whether these apps will work for you, but they are very small and work fine on my SYNDOME/Mustek Cypress semiconductor USB-Serial UPS running on Windows 10 64 bit.
Tiny download but nice status display and has shut down options. Very simple program with tiny memory footprint and minimal performance impact.
Another tiny download. Does not look as nice but has SMTP/HTTP and LAN network message notifications as well as shutdown options. All the usual information is there. An obvious choice if power event notifications are what your looking for.
Let me know in the comments if you found any other small free UPS monitoring software and I’ll add them to the list. Also let me know what other makes/models of UPS these programs work on for you.
After prolonged use by Linux of a shared NTFS drive in dual boot, Windows will report a corrupt disk, file system.
There is actually nothing wrong. Linux leaves the shared NTFS drive dirty on purpose to avoid file system corruption by windows fastboot. Over time of dual booting and not fixing then you might get some corruption.
If you have been using linux for a while then dual boot into windows 8 or 10, then do a disk check of your shared NTFS drive. Disk check will find errors, fix them, usually without any data loss.
You could turn off fastboot in windows to stop this happening. You could also disk check in windows regularly to fix the dirty flags, without disabling fastboot. That is up to you.
Comment if you need more information.
MSI installers, failing signed key. No encrypted or compressed temp folders. Windows 10 and a shared drive with Linux?
internal error 2755, 110 ?
If your sharing a NTFS drive with both windows and linux, then you may well lose some permissions on folders in the shared NTFS drive.
Even i f you are not sharing a NTFS drive in a dual boot system with windows 10 and linux yet you have these symptoms..
internal error 2755. 110 or ‘cannot open device or file specified’.
If you have already done the google and noticed you have no encrypted folders or files, then probably your linux is stripping some permissions from your dual boot shared drive.
Where you download your files,
- Right click your downloads folder and -> properties
- Security tab
- Enable inheritance
If your more with the security angle, then make sure SYSTEM has some access.
Another option is to copy the installer files to your windows boot drive. They will install fine from there without you having to mess with your shared drive permissions.