The problem with that, as I understand it: On Windows, you can change the drivers' INF files to use PID 0 with any text editor. You could do something similar on any OS. The problem is, the OS won't even try to load drivers for devices with PID 0. So you can't write a driver for that unless you intend to write a new driver for the USB chipset itself that remaps PID 0 devices to something else.

Image editing.

Audio production.

Design.

Page layout.

Video editing.

You know, a lot of professions.

Why is Apple even responsible for tracking that kind of information?

Can I sue them if they get it wrong, rendering my mail client unable to connect to the correct server (or revealing my credentials to a third party) because it followed their instructions instead of mine? No, that wasn't a typo, but thank you for redirecting my login credentials to the wrong server, which then stole them and used them...

Some guy gets bit by a kangaroo at the end.

Oh United, you so whimsical.

There's about 1 blue receptor to every 60 of the others.

Wellllll... kind of. When you're publicly traded, it's all about risk and paring down excesses. Shareholders don't want you to take risks. They want you play it safe so their share values don't go down. They want to see that you've cut operating expenses by X in every report. This limits your ability to try new things or market to those niches.

When you're private, you can take as big of a risk as your cash reserves permit.

You can't always, but you can prepare a recovery disk and also burn a copy of HBCD before your inevitable power cycle or reboot.

This system did not have a recovery partition, so no recovery mode on the HD, and it won't boot a restore disc... it was the perfect storm of garbage.

Otherwise I absolutely would have done a system restore.

Yep. That partition didn't exist on the affected machine because end user reasons, or I definitely would have tried it.

Indeed.

You could also boot with the install media and do a System Restore since Windows Update generates a checkpoint when you install updates.

If you don't have that option, my original solution will get you up and running, inconvenient as it may be.

This rollback procedure got my Win7 x64 system booting again:

From another system with the same bit width and service pack level, grab the files C:\Windows\System32\gdi32.dll and C:\Windows\System32\Win32k.sys.

Using HBCD or a similar boot disc, boot your defunct system. You can also snag the hard drive and plug it into another working computer.

BACK UP the gdi32.dll and win32k.sys files from System32 to another location just in case. Overwrite those two files in System32 with the ones you grabbed from the other system.

Your system is now bootable, having effectively rolled back the KB2982791 update. This is a quick and dirty procedure and leaves the update itself in an indeterminate state.

No no, upsell and upset are synonymous in this case. It's totally okay.

I wonder which direction the money flows in cases like this. Does Facebook pay the carrier, or does the carrier pay Facebook? Seems to me that both parties are equally at fault here. Some suits probably had a meeting about increasing shareholder value and leveraging popular apps and shook hands, then told the dev team to make it happen. Not that I'm thrilled with bundled software being possible on Android... I wish it wasn't... but it's not Android's fault that someone got greedy.

> Google's Android phones flat out REFUSE to uninstall Facebook, for example.

It uninstalls just fine, thank you very much.

Or are you referring specifically to Nexus devices?

I did this to a former roommate as well. He would have HD videos (Netflix, Youtube, etc) streaming on his computer AND game consoles at the same time, while he was uploading videos he was editing and downloading games and stuff like that.