Showing posts with label Windows. Show all posts
Showing posts with label Windows. Show all posts

Wednesday, November 1, 2017

Visual Studio Professional 2013 Crashes on Windows 10... A Solution!!!

So...  This morning Microsoft pushed down a large Windows 10 update.  My Outlook had been randomly crashing since installing Windows 10 so thought it would be a good idea to install the update.

After only...  30 minutes, the update was finished.  I started my normal every-day work programs like Chrome, Putty, SQL Server Management Studio, Excel, Outlook, etc...  Then I started my installation of Visual Studio Professional 2013.

Nope.  Wouldn't work.  Would simply lock up with this window (on the left) after just about 15 seconds.

Event Viewer showed the exception in two separate events:

First Event:
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentNullException
   at System.IO.MemoryStream..ctor(Byte[], Boolean)
   at System.IO.MemoryStream..ctor(Byte[])
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.Utilities.BitmapFromPngOrJpeg(Byte[], Microsoft.VisualStudio.Shell.Connected.ConnectedUser.Logger)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.AvatarCache+<>c__DisplayClass2.<.ctor>b__0()
   at Microsoft.VisualStudio.Shell.InvokableFunction`1[[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InvokeMethod()
   at Microsoft.VisualStudio.Shell.InvokableBase.Invoke()

Exception Info: System.ArgumentNullException
   at Microsoft.VisualStudio.Shell.ThreadHelper.InvokeOnUIThread(Microsoft.VisualStudio.Shell.InvokableBase)
   at Microsoft.VisualStudio.Shell.ThreadHelper.Invoke[[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Func`1<System.__Canon>)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.AvatarCache..ctor(Microsoft.VisualStudio.Services.Profile.AvatarSize, Byte[], Boolean, Microsoft.VisualStudio.Shell.Connected.ConnectedUser.Logger)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.AvatarCache..ctor(Microsoft.VisualStudio.Services.Profile.Avatar, Microsoft.VisualStudio.Shell.Connected.ConnectedUser.Logger)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.ProfileCache..ctor(Microsoft.VisualStudio.Services.Profile.Profile, System.Guid, System.Uri, System.String, Microsoft.VisualStudio.Shell.Connected.ConnectedUser.Logger)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.Connector+<ConnectAsync>d__1.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.IdeUserSession+<ConnectAndInitializeSessionAsync>d__a.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.BaseUserSession+<ConnectAsyncImpl>d__17.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.BaseUserSession+<ConnectAsync>d__2.MoveNext()

Second Event:
Faulting application name: devenv.exe, version: 12.0.21005.1, time stamp: 0x524fcb34
Faulting module name: KERNELBASE.dll, version: 10.0.16299.15, time stamp: 0x2cd1ce3d
Exception code: 0xe0434352
Fault offset: 0x001008b2
Faulting process id: 0x1958
Faulting application start time: 0x01d35325baa1390f
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: b0bb84fb-22a5-4efd-a88e-57bb6b1a32ca
Faulting package full name:
Faulting package-relative application ID: 

So...  After about 4 hours of poking on the internet and trying different things I found a solution that worked for me.  This will only work for people with valid logons to Microsoft MSDN who have access to Visual Studio.  (I am not certain how this would work for the free versions.)

  1. Run this in a command box:   DEVENV /resetuserdata 
  2. Add the line to the HOSTS file.
  3. Start Visual Studio 2013 and you should see a screen like the one below...
  4. Clicked Sign-Out on that screen.
  5. Remove the line added to the HOSTS file.
  6. Restart the computer.
  7. Go to MSDN website to get your Product Key for Visual Studio Pro 2013 (or whatever version you have installed.).
  8. Start Visual Studio.  
  9. When the User Information / Product Information screen pops up again, click “Change my product license.” 
  10. Enter your Product Key.
  11. Close Visual Studio and restart your computer one more time.

And, that's it.  My Visual Studio Professional 2013 is running fine once again.  Well, with one exception...  Now, every time I start it, I am prompted for my MSDN password.

There is mention that once you get VS running, you can select Tools -> Extensions and Updates -> Updates and install Update 5.  If you opt to try this upgrade install, be certain you have the time.  My upgrade is still downloading after 20 minutes.

Edit 1: Installing Update 5 does seem to complete the fix.


According to this reference, this specific problem started happening today...

Friday, February 3, 2017

What to do with all that speed???

So, computers based on quantum physics are already being planned, designed and in some cases even being created.  The electronics used in quantum computing do not rely on relatively slow semiconductors; they use near instantaneous quantum technology.  No, I don't know the details, but I do know that once some developers get access, there will be abstractions upon abstractions upon abstractions built, to the point where a quantum computer will perform about as well as a 80386 running OS/2.

Wednesday, July 8, 2015

8 Reasons for a New Operating System

Many years ago you could find me sitting in front of my computer wearing one of my well-worn Linux t-shirts or baseball caps, just programming my brains out, secretly wishing the universe of computers ran on one flavor of Linux or another.  Today, well, I am happy to simply have my Windows 7 machines humming along in front of me for at least a week without pause or crash.  Anyway...  over time I believe Linux has migrated from an OS that performed well & was fairly simple to install and operate, intended to make any computer geek giggle with delight, to something somewhat sloggy and overly complex that now give those same computer geeks headaches and the occasional nightmare.

Anyway, not that I have the technical ability in my current state, I would love to write a new operating system.  Why?  Here are eight reasons:

  1. Performance gains from increased hardware capabilities have been severely strangled by poorly performing code and the belief that the faster hardware will compensate for less than stellar code.  A new operating system should centrally focus on core performance at the expense of general purpose functionality.  
  2. Malware...  Viruses...  Keystroke Loggers... Spyware...  One of the key reasons this crap is proliferating is because we have the same-old operating systems and code and utilities.  A new operating system should have some basic security in mind when designing basic low-level functionality.  And, simply by nature, a new OS would be impervious to these nasties for a while.
  3. Current OSs are COMPLEX!!!  They try to be the do-all, know-all solution to everything.  Someone (or something) that tries to do everything will never do anything specific very well.  A new operating system should focus more on doing computery things, rather than everything under the sun.
  4. Developer environments and tools for Windows and Linux are fragmenting so badly, researching solutions and problems, depending on the situation, can be a near-futile exercise.  A new operating system could provide a new & clean slate.
  5. The windowing OS paradigm is dying.  Yes, I said it.  Don't get me wrong, the windowing paradigm will be around far longer than I.  However, it is my firm belief that virtual reality, tactile and audio human/computer interfacing will be the future.  A new operating system should have a low level text base interface for baseline operations, maintenance and debugging, and perhaps a windowing interface for coding, but should focus at these newer human/computer interfaces.  And, just as a note, all functions capable of being performed by the computer, should be allowed through the text interface.
  6. The Keep It Simple and Stupid concept has been, for the most part, thrown out by most modern operating systems and development tools.  A new operating system should embrace the KISS concept.
  7. Ever notice the slow access to directories with thousands of files?  OK, there may be solutions but it just peeves me off when I have 10,000 or 20,000 files in a directory and handling this many files is so slow (in both Windows and Linux) I can take an afternoon of coffee & smoke breaks.  A new operating system should minimally have the ability to support fast handling of large number of files.
  8. Provide a more rich computer eco-system.  Sometime I think Apple and Windows and Linux devs are getting lazy, just hunting for and polishing the low-hanging fruit.  A new operating system that performs well, has a vibrant development environment will place pressure on existing ecosystems and provide evolutionary pressure.
What are you waiting for???