Yesterday (2023-02-09), Chrome became excessively sluggish. It took 2+ minutes for the app to load. Google search results were quick, but it took minutes to load a page that took a fraction of a second in Edge.
I tried disabling all extensions, clearing all cache, running in incognito mode, restarting Windows, deleting my Chrome app data and uninstalling and reinstalling Chrome (without logging into Chrome), clearing temp files in app data, but nothing worked.
I finally tracked down the problem to Windows Updates.
I ran Chrome again this morning (2023-02-10) and found it still extremely slow. I installed the recommended Windows Updates, then re-ran Chrome. Chrome became responsive again.
The windows updates that were installed that seem to have fixed the issue are:
Windows Malicious Software Removal Tool x64 - v5.106 (KB890830)
2023-01 .NET 6.0.13 Security Update for x64 Client (KB5022546)
Intel Corporation - SoftwareComponent - 2.17.100.2
2022-12 .NET Core 3.1.32 Security Update for x64 Client (KB5021953)
2022-12 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 for x64 (KB5021089)
I'm not sure which combination of these updates fixed the problem, but I hope to limit others' frustration with this problem.
Related
It seems that there are issues with running and debugging Tizen .NET (Xamarin Forms) apps on Tizen emulators.
My environment is a Windows 10 machine, with the latest 2004 version. For development I tried both Visual Studio Professional 2019 (v16.6.2) and VS Professional 2017 (v15.9.24) with the VS Tools for Tizen extension.
I am able to deploy the application on the emulator however cannot debug, VS fails with the message Unable to start debugging. The system cannot find the specified file and in the console output I can see an the message [StdErr] error: cannot remove forward listener.
Does anyone have any idea? Is there some magical software combination that I can use to make this work or am I missing something?
I've experienced no end of troubles with Visual Studio Tools for Tizen. I nearly gave up today completely, I've spent weeks just getting it to partially work, and only a day or two of actual development, but finally figured out a few things that might be unique to my system or most likely are just missing in the documentation (which is not rare for Samsung at all).
First up, the emulator issue. I'm assuming you've been through the certificate manager and generated a Samsung certificate (make sure to have installed the extensions in the package manager, Samsung wearable extensions and Samsung certificate extensions then run through and create your Samsung certificate in certificate manager).
So now in the emulator manager try "right" clicking the specific emulator and select allow to install applications. It might now indicate it has installed a certificate. This is a good sign. Also i assume you know not to use HyperV (you can look up how to create a bootloader that can enable you to dual boot windows where HyperV can be disabled in one and enabled in your default).
Assuming that worked and you still can't debug i found that you may need to build the application (clean the build for good measure first - remember this - it can save you often if things don't work when you change something), then click Start without Debugging from visual studio. This should install the application to the device and launch it, fingers crossed. Now if that worked, and your application is now running in emulator or on device, you may find that future attempts now to debug it will work.
The final thing which has nearly made me give up is the update to my watch. It recently updated and i noted the new tizen version reported by the watch is 5.5. So naturally i went ahead and changed the api level to 5.5 and hey presto it all just seemed to work and i could continue as before, debugging and changing things happily. Then i uninstalled the application for a dry run and since then I spent a week trying to figure out why it will not reinstall the application on the emulator or the watch ( (it was a week ago i upgraded to api 5.5 and there were no issues, so that was way down the list of anything that could go wrong). I reinstalled etc, did the whole gamut of things all to no avail. At some point i got it working on the emulator but not the watch, finally today i have it working on both and don't wish to develop anything, i'm spent.
So that final issue was resoled by moving the projects back to api 4.0 and they would now reinstall on my watch and my emulator (use the Start without Debugging trick as well to install it first). Also (my fault - why it worked on emulator but not watch at some point) beware if you have one that is api 4 and one is api 5.5 - which i did while i was testing the above (one is a service the other the ui - they were at different api levels - that will not work on a device - but was happy on the emulator).
If none of that works for you, i'd advise give up, life is too short.
Cheers
I've recently upgraded my OS to Windows 10. I have a very basic Silverlight 5 application which gives me Unable to start Debugging. The Silverlight Developer Runtime Not Installed. Please Installed a matching version error in VS 2010 whenever I am trying to run the project.
I have :
Target Silverlight version is set to Silverlight 5 in web project.
I have installed Silverlight SDK, Silverlight5_Tools with SP1 installed & Silverlight Runtime which is 64-bit.
After doing all these steps and going through many online posts, still I'm unable to resolve this issue.
My Doubts are :
Do the Windows 10 upgrade has anything to do with this situation?
Windows 10 comes with a new browser Edge, is this because of this browser? Like Silverlight compability.
Again I am not sure but these are my doubt. Any suggestions?
Do you have a 64 bit OS ?
If so - uninstall Silverlight (developer!) and make sure you install the silverlight.exe (developer!) not the 64 bit version.
That worked for me.
HTH
Go to the properties of the Web folder start project. Click Web on the left tab. Unclick Silverlight in the debuggers.
Not a total solution but at least it allows you to debug other portions.
I had this issue and Uninstalling and Reinstalling didn't work.
Error in debug mode (F5 Debug solution configuration) was "Unable to start debugging. The Silverlight Developer Runtime is not installed"
In Debug configuration I would get the above error but finally I put the solution into release mode and it worked - then back to debug mode and everything worked without error.
Seems like a really odd fix but sure enough closing and re-opening the solution everything works now - Same install procedure as OP.
Another thing that's interesting is, the Debug only works in Chrome. If I target IE or edge I still get "Unable to start debugging. The Silverlight Developer Runtime is not installed"
I uninstalled Silverlight and then installed Silverlight_Developer.exe. I also switched default browser in Visual Studio to Internet Explorer (I have Edge otherwise which won't work...).
Nice to see some more people also using Silverlight these days, hehehe.
This is a really old thread, but I just ran into this issue with a project. I was getting the message that the Developer runtime was not installed, but in fact it was, and another similar project ran just fine on the same machine with the same version of VS 2015.
The fix was to ensure that the startup project is the WEB project, not the Silverlight project. Somehow, the default startup project got switched to the SL project. After I switched back, then it worked just fine.
Ever since upgrading to Azure SDK 1.8 we have been consistently having extremely long delays when switching between build configurations in VS2010. It can take several minutes to switch between a debug and release build. We also see the VS window minimize itself and maximize itself at times during the switch.
This happens 100% of the time on every machine that has been upgraded all Windows 7. We performed the manual install as per the instructions on this page: http://www.microsoft.com/en-us/download/details.aspx?id=35448
Anyone else seeing this?
Have you tried installing the latest "Windows Azure SDK for .NET (VS 2010 SP1) - 2.1" through the Web Platform Installer? I think it should clear those issues.
Here is a direct link to the Microsoft Download page as well:
http://www.microsoft.com/en-ca/download/details.aspx?id=39708
I am developing an application for Windows Phone in Visual studio 2010 ultimate using wp7.1 SDK in Windows 7 32 bit and 3GB RAM. My system often gets stuck and then restarts sometimes when I run the application on wp7 Emulator (2 or 3 times an hour). Before restart it displays the message: "Display driver stopped responding and recovered" and leads to a blue screen displaying "some lines with Contact system admin".
I am not sure why, will need more details. Try installing the 7.1.1 update for the SDK, it is meant for low profile devices, but I am just hoping this will resolve your issues too.
http://www.microsoft.com/en-us/download/details.aspx?id=29233
Had the same problem. Just start your sdk installer. There will be a option of repair of deleat. I repaired my sdk first but it still did not work. I then deleted my sdk and reinstalled it. Worked like a charm.
But you must you know that I was not able to delete my sdk too. My antivirus was doing something wrong and stopping the uninstall of my sdk. So I had to delete my antivirus... than my sdk. Than reinstall the sdk, reinstall the antivirus.
It all worked great after.
I'm a .Net developer running Windows 7 Ultimate (x64) on a 2010 MacPro (2.27Ghz/6GB RAM) using Bootcamp. Until about a month ago its been, imo, the ultimate dev workstation. However recently I've noticed that Visual Studio 2010 takes a very long time to redraw its windows. This is most noticeable when switching to it after its been in the foreground.
I don't get this problem with other Windows apps and am baffled because the machine has more than enough grunt to handle a few MDI'd windows yet grinds for up to five minutes sometimes when reactivating the VS environment - the screen update seems to slow everything down. My colleagues are using identical hardware and software but running Windows under Parallels on their Macs does not lead to this behaviour.
I'm getting desperate (and I've asked this same question at apple.stackexchange.com) - does anyone know why this might be happening and whether there's a fix ...?
Improving Performance by Changing the Visual Experience
You might have a problem with Hardware Acceleration in VS2010. I had an issue with rendering applications built using WPF because of this.
Give it a try:
http://blogs.msdn.com/b/zainnab/archive/2010/06/22/improving-performance-by-changing-the-visual-experience-vstipenv0017.aspx
And if that doesn't fix your issue, go to your video card settings (nvidia or amd) and do a "reset settings". Then try again.