FUCK YOU TOO MICROSOFT! Title is invalid
-
I installed VS2015 Community Edition yesterday, and during the multi-hour long install, it made several snapshots of my system, using the Shadow Copy service, I suppose. Great idea!
So I turn my computer on this morning, and it had some problems starting up. I recovered to the last snapshot that VS made. I'm sure glad VS made a snapshot of a clean system after the install!
When I finally booted up, it turns out VS wasn't fully installed. Hmm, okay. Still, it's better than nothing!
So I wait about an hour while VS finishes its install. I try loading it up, and it immediately bitches about Python Tools not being connected or something. HMMM, WTF IS THIS.
I ran the installer, and set it to repair the installation. That took like two hours, but it finished. I loaded up VS again. SAME PYTHON TOOLS ERROR. Fuck it, I'll skip that stupid error, since it gives me the option, and I'm not planning on using Python for this project.
So I make a new C# project. It immediately bitches about something else. Oh wait, I can't even close VS, because it keeps pooping up that same error message. It took a force quit to reboot to make it shut the fuck up.
Microsoft, for when Linux doesn't fuck up enough.
-
(post withdrawn by author, will be automatically deleted in 42 hours unless flagged)
-
Oh boy here we go again.
Could not load file or assembly 'Microsoft.VisualStudio.ConnectedServices, Version=2.0.0.0, Culter=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
-
-
Yeah, it's partially installed and probably shat itself hard...
-
How is that a WTF? Why would it make a snapshot of a broken state? What are the snapshots for if it can't recover from the snapshot state?
-
How should it know it isn't in a correct state? Magic?
-
By checking?
Or by actually doing something useful when I hit the repair button?
It knew that it needed to continue the install when I booted it up this morning...
-
How is that a WTF?
The same way clicking ads that say "WE FOUND 498 PROBLEMS WITH YOUR COMPUTER. CLICK HERE TO FIX THEM" is. You should be computer-savvy enough by now to know that Windows's System Restore does anything but system restore.What are the snapshots for if it can't recover from the snapshot state?
For all I know, it's there to trick users with broken systems into breaking them even more.
-
Windows's System Restore does anything but system restore.
That doesn't make me the WTF... that makes Microsoft the WTF.
For all I know, it's there to trick users with broken systems into breaking them even more.
Fine, but that doesn't make me the WTF.
-
Why would it make a snapshot of a broken state?
Because it's installing sub-components and WIndows makes a snapshot most all of the time whenever something installs. Why would you think it would work?
BTW, I don't disagree that VS's install process is a WTF, nor that failing like that is a WTF, just that you expecting a restore midway through the install to work is also a WTF
-
BTW, I don't disagree that VS's install process is a WTF, nor that failing like that is a WTF, just that you expecting a restore midway through the install to work is also a WTF
If it hadn't advertised that it does snapshots, and then continued from where it left off, I wouldn't have expected it to work.
-
I guess I'm more cynical than you, but I'd never think that would work, even if it says it would.
A full restore to before the installer launched should work fine though
-
I blame it on third-party extensions and Linux hardware.
-
That doesn't make me the WTF... that makes Microsoft the WTF.
Yes, they're WTF too. But what makes you WTF is that you've fallen for their prank. Regular users have the excuse of the text claiming to fix problems they have, and they believed it because MS is pretty legit source. You, as a professional, don't have this excuse, as you should be experienced enough to know better.
-
I may have to try that. I'm doing a full uninstall now, and if it doesn't work, I'll nuke the motherfucker from various orbits, up to a full system install if necessary.
-
-
What are the snapshots for if it can't recover from the snapshot state?
The snapshots are for the OS itself, not the millions of different programs that can be installed; if they covered the whole system, it would take far too long to make a snapshot, and the snapshots would be massive.
-
I may have to try that. I'm doing a full uninstall now, and if it doesn't work, I'll nuke the motherfucker from various orbits, up to a full system install if necessary.
Make sure you google the magic incantation. Because simply using the installer to uninstall leaves mountains of shit behind. (because something else might be using it too)
-
Windows's System Restore does anything but system restore.
It's saved my ass every time I've needed it. A++ would restore again.
-
-
The snapshots are for the OS itself
Yes. This makes for much fun when half of a program's configuration is in the Registry, and half is in the User Profile, and half is in the Public User's profile, and half is in its own Program Files folder.
-
Yes. This makes for much fun when half of a program's configuration is in the Registry, and half is in the User Profile, and half is in the Public User's profile, and half is in its own Program Files folder.
That totals to two program configurations.
-
-
-
-
-
Windows is in a functional state. There's nothing broken about Windows. But that doesn't mean the whole system correctly remembers that it was mid-install for Visual Studio.
Do a full uninstall, make sure your system is fully patched, make sure you have as much disk space as you can, reboot, and then install Visual Studio again.
-
-
HURR :fa-vomit:
I just did that. Same error. I'll have to nuke this machine tomorrow. Which is the last thing I need right now, since I was almost caught up.
-
I'll have to nuke this machine tomorrow.
Makes me glad a lot of my stuff is stored on snapshot-ed VMs...
Filed under: But a lot of my stuff is similarly not on said VMs, so I suppose TRWTF is on me
-
-
I wish Microsoft would come up with a simple way to handle adding and removing apps. Their own installers, as shown, are rickety and fragile, both in Win32 land and Windows Store land; the former having very sketchy error handling and rollback support, the latter just breaking all the time for no obvious reason. There is a LOT to be said for OS X's "it's just a dumb folder" approach to applications.
-
the former having very sketchy error handling and rollback support,
No, it (MSI) has good support. Now if people actually treated MSI creation in the same way as writing the program it's installing, maybe the installers would be better.
-
I wish Microsoft would come up with a simple way to handle adding and removing apps.
They have two: MSI and Chocolatey.Of course, that relies on people making MSI installers that don't suck...
-
f course, that relies on people making MSI installers that don't suck...
We're talking about real world things here, not flights of fancy from our imagination...
-
We're talking about real world things here, not flights of fancy from our imagination...
Yeah, but that's not Microsoft's fault! Back to the whole bad programmers are write bad programs thing.
-
-
Makes me glad a lot of my stuff is stored on snapshot-ed VMs...
Maybe I should just start putting some of my stuff in snapshotted VMs. Or all my stuff. Each app in a VM with a base VM containing the OS so the linked ones will only have to store the altered files. And then add a shared folder to store my documents, and maybe add some intercommunication APIs so I can seamlessly share data by copying and pasting between windows.
Oh look I just invented operating systems. Except this one would work fine since it would actually isolate each application's files and data.
-
Only install method that is acceptable IMO is what is called a "xcopy" install, where the application won't put anything outside it's own directory. That also excludes most of Linux-based OS standards, but whatever.
-
Oh look I just invented
operating systemscontainersYou forgot the overlay runner, which invokes each application in the VM you want to run as a seamless RemoteApp on the console session.
After that, you would have something very similar to what I run on at home!
Filed under: Oh wait, you're probably being sarcastic, aren't you...
-
So what's going wrong that virtually every Microsoft-made application for Windows has a terrible, barely functional installer that frequently falls over for no reason whatsoever, craps on everything when it does so (newer VS installs often trash older ones in subtle ways) and as above doesn't roll back well? SQL Server included. Heck, for Visual Studio Code they recently gave up trying to use their own tools and use Inno Setup now.
If the company that made the tool can't use it effectively, it is quite objectively a bad tool.
-
Only install method that is acceptable IMO is what is called a "xcopy" install, where the application won't put anything outside it's own directory. That also excludes most of Linux-based OS standards, but whatever.
Sure, if you don't mind having a million copies of identical libraries filling up your hard drive
-
I don't
-
the multi-hour long install
At the risk of , sounds like your computer's TRWTF here. It shouldn't take anywhere near that long.
And that's before you get to the actual problem you had.
-
He might be using the web installer over a shit Internet connection
-
He might be using the web installer over a shit Internet connection
Well, that's still some kind of TRWTF.
-
(because something else might be using it too)
There are worse aspect of this problem. If some softwares does not use standard installer so they use some of the components without increasing the reference count, when you install one software package, it could break other such softwares (Any component in the package that reach reference count 0 on uninstall will be removed too).
-
Before you doing that, it could be better to actually try this.
-
Of course, that relies on people making MSI installers that don't suck...
... and actually deploy updates to their application through .MSP file, so the installer database can know what exactly to do when you need to uninstall it.