Drag and Drop files in Windows 7 with User Account Control (UAC) enabled causes issues.

I took the plunge and updated to Windows 7 x64 on my development machine. It has been a fairly pleasant experience for the most part. No major problems with installation, setup, drivers, or getting my development environment configured correctly so that I can get back to working!

I’ve been enjoying Windows 7 so much that I decided to leave the User Account Control (UAC) active. The implementation seems to be MUCH less annoying in Windows 7 than it was in Windows Vista. You even have access to options to configure just how annoying (err, I mean secure) you want it to be.

Unfortunately, I found a deal-breaker that finally led me to disable the UAC in Windows 7. The problem started out when I was unable to drag an aspx file from my Windows Explorer window into my Visual Studio window like I’ve always done. I ended up figuring out the problem. I had the “Run as Administrator” option set for my instance of Visual Studio 2008 while my Windows Explorer was running with default permissions for my User Account. >_<

UAC is trying to protect me from processes running with lesser privileges from sending messages to processes running with Administrator privileges. Probably a valid concern, but considering that I generally NEED to run my Visual Studio as an Administrator and I really like the ability to drag an drop files into it… UAC has gone the way of the Dodo once more (at least on my machine.) I also ran into this issue when trying to drag files into my SQL Server 2008 Management Studio. This one isn’t as critical since it really doesn’t need to be run as Administrator, but annoying just the same.

Hope this might help someone else figure out why Dragging and Dropping between processes no longer works for them in some instances!

~ Paul

Facebook changed my language setting on me - Unrequested Language Change

While I was checking my Facebook today, I ran into a strange issue. All of my menus, status updates, recent updates, requests, suggestion, and pretty much everything else changed to another language. I didn’t change any settings or update anything, i was just reading the updates on my home page. See the screenshot below.



Seeing that everything was in this new and interesting language, I couldn’t exactly get into my facebook settings and find out where to change the language back. Fortunately I found a direct link to the Facebook language settings page so that I could change it back to my native English. You can click the link below to check it out and fix this issue.

Facebook Language Settings Direct Link

Hopefully Facebook find out how my setting suddenly and randomly changed and I hope this helps someone else out if it happens to them.
~ Paul

Encountering a Black Screen after logging into another computer with Window Remote Desktop Connection

I had to Remote Desktop into a Windows Server 2008 machine for a client today and encountered a Black Screen after successfully logging in. No matter what I did, I couldn’t get the screen to go away. I tried all my normal tricks such as spamming ctrl+alt+delete and yelling at the screen, but nothing seemed to work. The next step was to Google it…

The Google results were plentiful and recommended that I disable Bitmap Caching from the Experience tab of the Remote Desktop Connection window. I do so and re-connected. No luck for me, but many others reported that this fixed it for them.

The next most common Google result was to check firewall, router MTU, and other router settings. Since my remote desktop connection have never had trouble before and I was able to successfully log into the same machine under a different user name, I figured I’d skip that one.

My next idea was to try and log in with another account. I logged in with the administrator account and found that it was working fine. My immediate thought was to try to find my other logged in session and force a log out. Supposedly, you can view logged on user by opening your  Server Manager, expanding File Services, clicking on Share and Storage Management, and then clicking on Manage Sessions in the action pane to the right. This did not work for me (my other session wasn’t listed,) but it might for you. =)

After trying all of these “fixes” I decided to just do what I needed to do from the Administrator account that I was logged onto. By the time I was finished, I switched back to my other Remote Desktop Connection screen and was surprised to see that it was no longer black, but was showing the login window again. The session must have timed out and locked. I logged in and everything seemed to be working correctly again.

I’m not sure if allowing the session to time out and lock was what fixed it or if Remote Desktop just needed some extra time… But hopefully something in this post helps you out if you encounter a Black Screen after logging into a Remote Desktop session.

~ Paul