4 ms·

I was trying to install Star Wars: The Old Republic, and the Visual C++ 2008 Redistributable flat-out refused to install die to "Error 1365" (if I remember my e

I was trying to install Star Wars: The Old Republic, and the Visual C++ 2008 Redistributable flat-out refused to install die to "Error 1365" (if I remember my error codes right). Required a Microsoft FixIt to fix the registry keys. And I have no idea how it happened.

sukuriant 15y ago
That is quite curious... though can you really blame the operating system for a program running on it? (Presumably SW:tOR)
- Lewisham 15y ago
  I can certainly blame Microsoft for Microsoft libraries that don't install on its own operating system cleanly, and requires a Microsoft-issued fix.
  - sukuriant 15y ago
    I don't know, but maybe SW:tOR didn't do proper checks and so it was trying to install something antiquated, and modified the registry beforehand?
- tedunangst 15y ago
  People like to blame everything on Windows, including "I dropped my laptop down the stairs and now it doesn't work right" type stuff. I think if Microsoft had replaced the blue screen with a message that instead said "Your $PC-MAKER computer is a piece of crap, buy a $OTHER-PC instead." nobody would actually complain about Windows. [a general comment, not directly related to lewisham's problem.]
  - barend 15y ago
    In some regards, they did. The crash reports from Windows XP indicated that around 20% of all OS crashes originated in the display driver (1). Vista introduced a new display driver model. One of its features is that the OS will now survive a driver crash. The screen just goes blank for a few seconds. 1) http://msdn.microsoft.com/en-us/library/aa480220.aspx http://msdn.microsoft.com/en-us/library/aa480220.aspx
- philwelch 15y ago
  I've never installed SW:tOR on a Mac, so I can't say for sure, but I've never corrupted my operating system by installing an application before. That kind of bullshit actually is the fault of the OS.
  - vacri 15y ago
    The guy does't sound like an advanced user and may be using a sledgehammer to pound in a nail. He's not complaining of bluescreens, he's complaining of corrupt registry keys, which can do as little as preventing the one app from installing the way he wants. Reinstalling Windows is a sledgehammer here. Looking up his error code, all he needed to do was reregister the library. If he's not an advanced user and so doesn't feel comfortable using the CLI, then it's not surprising a tool would be used. But reinstalling Windows to resolve this is like rebooting your computer because you want to turn caps lock off.
    - philwelch 15y ago
      The technology has existed for decades to install applications without having to make potentially dangerous alterations to systemwide shared state. There's only so much you can blame on app developers. In the year 2011, shipping an OS that allows an application to corrupt the registry is just as stupid, if not stupider, than shipping an OS that allows the application to grab or generate arbitrary pointers into memory allocated to other processes. No one should have to know what "reregister the library" even means.
      - vacri 15y ago
        The problem here is that you think 'corrupted registry keys' means that the computer is unusable. A corrupted registry key just means that a setting hasn't been saved right - it could be as trivial as whether an app starts fullscreen or windowed. The GP's statement did not say that the system was faulty, just that he was experiencing errors and he reinstalled. On enquiry, they weren't system errors, but errors around the installation of a program, for which he sledgehammered the result. You don't need the "Visual C++ 2008 Redistributable" to run Windows, or a great many things on windows. It wasn't the operating system blue-screening. No one should have to know what "reregister the library" even means. We're in 2011, no-one should have to know what 'engine oil change' means either, but someone still has to know how to do it.

sukuriant 15y ago

That is quite curious... though can you really blame the operating system for a program running on it? (Presumably SW:tOR)

Lewisham 15y ago
I can certainly blame Microsoft for Microsoft libraries that don't install on its own operating system cleanly, and requires a Microsoft-issued fix.
- sukuriant 15y ago
  I don't know, but maybe SW:tOR didn't do proper checks and so it was trying to install something antiquated, and modified the registry beforehand?
tedunangst 15y ago
People like to blame everything on Windows, including "I dropped my laptop down the stairs and now it doesn't work right" type stuff. I think if Microsoft had replaced the blue screen with a message that instead said "Your $PC-MAKER computer is a piece of crap, buy a $OTHER-PC instead." nobody would actually complain about Windows. [a general comment, not directly related to lewisham's problem.]
- barend 15y ago
  In some regards, they did. The crash reports from Windows XP indicated that around 20% of all OS crashes originated in the display driver (1). Vista introduced a new display driver model. One of its features is that the OS will now survive a driver crash. The screen just goes blank for a few seconds. 1) http://msdn.microsoft.com/en-us/library/aa480220.aspx http://msdn.microsoft.com/en-us/library/aa480220.aspx
philwelch 15y ago
I've never installed SW:tOR on a Mac, so I can't say for sure, but I've never corrupted my operating system by installing an application before. That kind of bullshit actually is the fault of the OS.
- vacri 15y ago
  The guy does't sound like an advanced user and may be using a sledgehammer to pound in a nail. He's not complaining of bluescreens, he's complaining of corrupt registry keys, which can do as little as preventing the one app from installing the way he wants. Reinstalling Windows is a sledgehammer here. Looking up his error code, all he needed to do was reregister the library. If he's not an advanced user and so doesn't feel comfortable using the CLI, then it's not surprising a tool would be used. But reinstalling Windows to resolve this is like rebooting your computer because you want to turn caps lock off.
  - philwelch 15y ago
    The technology has existed for decades to install applications without having to make potentially dangerous alterations to systemwide shared state. There's only so much you can blame on app developers. In the year 2011, shipping an OS that allows an application to corrupt the registry is just as stupid, if not stupider, than shipping an OS that allows the application to grab or generate arbitrary pointers into memory allocated to other processes. No one should have to know what "reregister the library" even means.
    - vacri 15y ago
      The problem here is that you think 'corrupted registry keys' means that the computer is unusable. A corrupted registry key just means that a setting hasn't been saved right - it could be as trivial as whether an app starts fullscreen or windowed. The GP's statement did not say that the system was faulty, just that he was experiencing errors and he reinstalled. On enquiry, they weren't system errors, but errors around the installation of a program, for which he sledgehammered the result. You don't need the "Visual C++ 2008 Redistributable" to run Windows, or a great many things on windows. It wasn't the operating system blue-screening. No one should have to know what "reregister the library" even means. We're in 2011, no-one should have to know what 'engine oil change' means either, but someone still has to know how to do it.