Use this trick to get the serial number of your hard drive in Windows 10 + 8 & 7 without physically taking it out and looking at the sticker!
It’s really simple and only takes a second if you follow these instructions!
Use this trick to get the serial number of your hard drive in Windows 10 + 8 & 7 without physically taking it out and looking at the sticker!
It’s really simple and only takes a second if you follow these instructions!
After upgrading to Windows 10, I have had some issues with a couple of RDP connections that wouldn’t store the username and password (credentials). Despite ticking the box to save the credentials, it would always prompt me to enter the password.
Here’s how to fix the issue with RDP not saving the login information, which should work not just on Windows 10, but also other versions of Windows if you have the same problem Continue reading
If the Alt Gr key stops working, close Remote Desktop Connection if it is open. Try it out now!
There’s an old bug that causes the Alt-Gr button on your keyboard to mysteriously malfunction.
This is an old problem which still persists on Windows 10.
This bug has been plaguing me and others for many, many years. Since we use the AltGr key to produce the @ (at) sign here in Norway,
Even in 2019, I still get this problem all the time.
I just wanted to share the solution in case anyone else has the same issue, so hopefully it helped you out if you’re reading this, if not, please leave a comment!
PS! You can still try to help by voting for this Alt Gr bug to get fixed.
Either search for “Feedback Hub” on Windows 10 and log in if it asks you to.
Then click here.
Or, alternatively, open Edge in Windows 10, and paste this into the URL (address) bar:
feedback-hub:?contextid=937&feedbackid=bbb4ec30-a366-47c0-bc4b-610604517539&form=1&src=1
Thanks to Slingshot in the comments for this initiative!
Currently I am using Remote Desktop on Windows 10 to connect to a Windows 7 computer regularly. This has worked flawlessly for months.
Suddenly I started to experience that Remote Desktop would crash whenever I clicked on a folder in Windows Explorer on the remote computer.
I had some problems with the Windows Shares becoming unavailable at odd times, just randomly now and then. This meant I could no longer list and open my media files from my LG Home Theater or my Raspberry Pi.
I discovered that restarting a few services associated with Windows Folder Sharing solved the problem without the need to reboot.
This is a quick little script that I use to re-map my shared folders in Windows, including the disk shares (i.e. d$, e$) every night:
net stop LanmanServer /y
net start LanManServer
net start Browser
net start HomeGroupListener
Copy these lines in to a text-file using Notepad and save the file as “Sharemap.bat”, for example.
To set up an automatic scheduled job to run the script, open Task Scheduler (Start -> Run -> taskschd.msc) and set up a basic task: Right-click the folder area on the left and select “Create basic task”.
For the actions pane, select “Start a program” and point to the Sharemap.bat script.
For the triggers, you can set it to run every night at 5 in the morning or something similar.
If you’re using TrueCrypt and need to make disk shares (d$, e$ etc) map up after TrueCrypt mapping has taken place, create a trigger and set it to run “At log on”, with a delay that’s long enough to allow you to mount the TrueCrypt volumes before it runs (5-10 minutes maybe).
Alternatively, you can simply create a shortcut to “sharemap.bat” or save the file directly to your desktop and run it manually as needed.
How it works:
Stopping the LanmanServer service automatically stops the child services Browser and HomeGroupListener as well, automagically – so we only need to start those services, or at least I chose to do it that way to be on the safe side.
These network services are responsible for making Windows Shares available on the network, so it is sometimes necessary to restart them if there are any issues with finding shares, especially disk shares that are not automatically mapped by Windows, caused perhaps by delayed mounting from TrueCrypt or similar applications.
The only built-in “wallpaper mode” that works with multiple monitor wallpapers is the “tile” mode. However, it didn’t work correctly on my setup, as it kind of started on the wrong display due to the internal “ranking” of my monitors, making the result look like so: