The context menu (right-click menu) takes a lot of time in appearing. Sometimes when the user right-clicks, the OS freezes for a few seconds and then it starts working again. So basically the issue occurs when you right-click on Desktop and the context menu takes longer time in displaying. Let me tell you, it's not a fault of the operating system.

• Right Clicking Files Takes Forever
• Right Clicking On Desktop Takes Forever Windows 7

After upgrading both SQL Server and Management Studio from 2008 to 2012, Management Studio 2012 is very slow when new query windows and dialog boxes are opened.Even right clicking on tables is slow. There is typically at least a 5 second delay before I can start doing anything within a window. This happens every time, even if I open the same window twice in a row. Why does this happen and how can I fix it?Other applications establish connections to the database very fast.Things I have tried that did not help:.

A hit on Google where I'd need to modify my hosts file. Resetting SSMS 'user-defined settings'. Updating video drivers, turning off hardware acceleration, disabling DirectX.

Disabling the Biometric Authentication Service (I don't have it installed).My computer should be more than fast enough, and I also have 16GB RAM. My hardware should definitely not be a problem. It looks like SSMS is waiting for something - I can operate other programs smoothly while this is happening.I don't have the opportunity to install the SQL Server 2012 CU1 update because there seems to be some risk of errors installing hotfixes and I can't risk that right now. SQL Server Management Studio StartupWhen Microsoft's SQL Server Management Studio (SSMS) starts it tries to connect the Certificate Revocation List (CRL) of Microsoft:The underlying.NET components of SSMS are trying to contact the Certificate Revocation List and SSMS is unable to do so.

This slows down the overall loading procedure. (15 seconds per certificate apparently)Ok so here is what is happening. SSMS has a high percentage of managed code, all of this code is signed when we ship it. At start up (if this setting is checked) the.Net Runtime tries to contact crl.microsoft.com to ensure that the cert is valid(there were some fake certs issued in Microsoft’s name a while back so this is a very valid concern). If there is no internet connection or there is a problem contacting the certificate revocation list server then this will delay SSMS startup.Reference:One issue that can cause this problem is that if the server does not have access to the internet, then the.NET framework can’t access the crl.microsoft.com website to verify that the digital signatures used to sign the binaries for managed applications are valid.

Each certificate check has a 15 second timeout in the.NET runtime implementation. It might have happened that SSMS has imported settings that can not be treated correctly anymore (like connections to some server or maybe some add-in settings).There is a brutal way to 'reset' user-defined settings of SSMS.Close SSMS, go to folder: C:UsersYOURWINLOGINNAMEAppDataRoamingMicrosoftSQL Server Management StudioYou will find subfolder '11.0'.

Right Clicking Files Takes Forever

Rename it to '11.0', so you can always rename it back. Now start SSMS - it will re-create clean settings and maybe your problem will be solved.

If not - delete newly generated '11.0' and rename '11.0' back to '11.0'.This also might be a behaviour of some add-in, that got corrupted after upgrade. Add-ins register themselves as handlers for some commands or events and system might get unstable if they are missing/throwing exceptions.Actually, v2012 uses another mechanism for registering add-ins, but some add-ins install themselves on all instances. To check, look into this registry key: HKEYCURRENTUSERSoftwareMicrosoftSQL Server Management Studio11.0ConfigAutomationOptionsLookInFolderYou will find folders list there. Check all these folders - they must be empty (means you have no add-ins). I have not personally experienced this issue, however there is a long thread where many people have. The general advice seems to be to related to working with your video driver by either. Installing an updated video driver -OR-.

Reducing or turning off hardware exceleration -OR-. Turning off DirectX supportFrom the thread there was also this answer.' Windows 7 Clean Boot procedure revealed the service Biometric Authentication Service (DigitalPersona DPHostw.exe) was the problem. Disabling the service fixed the problem.' I would be interested to know if any of these approaches work in your case as well, as the thread I found relates to older versions of SSMS, i.e. 2005, 2008, etc. I would guess the problem is that opening a new connection to your server takes 5 seconds.

Why exactly this is the case I cannot tell and it would require a wire trace to analyze and diagnose. You should investigate what protocol(s) are being attempted and what protocol eventually succeed. It could be that your client attempts named pipes first (which depends on SMB) and then falls back to TCP (although the usual delay in such a case is much longer, around 20-30s seconds).I would recommend you check the order of client protocols in the. Check the client used protocol by finding your own entry in. I too was experiencing a 5 to 10 second delay when right-clicking a table to pull up the context menu. My situation might be a little different than some however because I use local databases only. My solution:After reading the answer from imran about disabling antivirus, I took that concept a step further since I do not want to disable my antivirus completely JUST to overcome this issue.I have reduce the delay significantly (it is now 1 second max) by changing the default database locations and then excluding that directory from the anti-virus (in my case I am using Microsoft System Center Endpoint Protection 2015).For changing the default database locations see the following article for detailed information.

I had the same problem with SSMS 2016. I used to identify that the last thing it did before a several-second delay was make a network connection to a Microsoft IP address.

I then tried turning off the Customer Experience Program by setting registry key HKEYCURRENTUSERSOFTWAREMicrosoftMicrosoft SQL Server130 value CustomerFeedback from 1 to 0. After restarting SSMS it's working fast again. Presumably that doesn't always lead to slow new query windows but for me it did.I don't know if that's what was going on with your SSMS 2012 but perhaps worth a try. Registry key will probably be 110 instead of 130. I have ssms v17.0, I also had the problem with slow right click context menus.The name of the computer had dashes in it, renaming the computer something simple, fixed it.I uninstalled ssms, uninstalled sql server, renamed the computer something simple like 'MyBox' instead 'xja-13-asdfa3'. Then I reinstalled sql server, then ssms, and this fixed ALL my SLOW context menu problems when right clicking tables.

I imagine that somewhere DNS problems were occurring and the waits were related to waiting for dns timeouts.I had a laptop with 16 gig of ram, ssd drives, a 3ghz cpu straight out of the box from the factory with the default random pc name.

Surender Mohan Pathak – WikipediaAmazon Restaurants Food delivery from local restaurants. The ‘philosopher’ detective Sudhir Kohli is another series character of Pathak. Get fast, free shipping with Amazon Prime. It carries the prestige of over 47 years of retail experience. Mujhse bura koi nahi. Story of extraordinary tricks and cons of Conman who was adept at conning young and beautiful girls.

If you are running a fast computer with enough RAM where excessive disk thrashing is not supposed to take place, I believe it could be some program running in the background causing the problem.I'm the kind of user that can't be bothered with slowdowns of this nature. At most times, I have my computer running the following programs in the background: ZoneAlarm, Trillian, iTouch (logitech keyboard) & the UD Client.You know, the first and most important reason why I have all these is because none cause abnormal slowdowns, otherwise I could live without any of them.Antivirus utilities, I believe, can cause such problems, same goes with all non fine-tuned programs in general or beta versions of them. Look for all programs running in your computer when you start up, look in the startup folder and in your registry and try to run the minimum number of programs possible. Now ive noticed that the problem not only occurrs when right clicking a file or folder, it also happens when I select a file or folder and then click on 'file' in the menu bar. The menu hangs for about 5 seconds before displaying the available options for the file or folder. I also disabled almost all the programs in the context menu but that didn麓t help.

Another strange thing is that the problem occurs with all files or folders including shortcut icons Except for url files and other windows icons like 'my computer' and 'recycle bin'. The problem doesnt occur if the file selected is an url or if it is a shortcut icon targeted at an url file. If I create any file and right click on it the problem ocurrs, but if I change the file extension to '.url', the problem doesnt ocurr.I have narrowed it down and apparently the problem actually is the network adapter. First I tried booting in safe mode and the problem didnt occur. Then I uninstalled the network card and uppon rebooting i got an error message saying 'Exception on ESockError in module shellapi.exe at 0008: Socket operation in non-socket', however, the rigth clicking problem stopped. The error message dissapears if I reinstall the network adapter. I had seen the error message before installing this specific nic, it happened with another nic when I uninstalled and reinstalled it to make my computer the host for the internet connection instead of a client sharing the connection.

That network card did not detect my dsl modem so I installed the current one. Ive tried installing new drivers for the nic but it doesnt help. Sounds like your Registry is pretty hosed at this point. I'd suggest a fresh Windows install.When I first got DSL I used the software that came with it.

It was Enternet 300 connection software. It caused all sorts of annoying problems. Even uninstalling it didn't fix the problems it caused. Now I have a Linksys DSL Router and with a clean install of Windows everything is happy. No more need for DSL PPPOE software; Just tell the Router your username and password once and no more logging in. When you start the computer the NIC automattically is connected and on the internet.

Right Clicking On Desktop Takes Forever Windows 7

Getting a DSL router is worth it even if you have only one computer. Far less hassle than the crud your provider makes you install.