Salta al contenuto principale

Update to latest fails

Thread needs solution

I was running True Image 2012 today (Dec 7) and it said there was an update...build 6131 I assume. It started downloading and then started installing the update but then blue screened (0x00000023). bluescreenview says the problem was with the fastfat.sys driver. No problem, I rebooted my computer and now I get the startup repair screen and it finds a problem with fltsrv.sys missing or corrupt, I assume because of the failed upgrade.

What's going on here? My computer never blue screens so this is very unusual. I'm now trying to get my Windows 7 x64 machine to boot.....not impressed.

0 Users found this helpful

I can't guarantee that this will address what's causing the prob but it's quite possible that the updating corrupted the program.
try unistalling, running the cleaner and then installing the lastest downloaded version.

Or better, restore a backup of your machine to a time prior to the the attempted up date, then unistall and try to install the newer build.

In eighter case, use msconfig.exe to diable all non-microsoft srvices and all startup programs before unistalling/installing. This isn't usually necessary but it guards against any program conflicts mucking up the installation.

I too had a failure trying to install an update. The new process does not allow me to download (I don't think) so I don't know which build it is. I am reluctant to try it again because it rendered TI 2012 completely unusable and uninstall would not complete.

Fortunately, I had done a full backup the night before and was able to restore my system pre-update.

Allegato Dimensione
85612-98569.txt 10.69 MB

WP wrote:
What's going on here? My computer never blue screens so this is very unusual.

It's quite simple really. You just have to understand that software products developed by Acronis programmers function on the same basis as the little girl in the nursery rhyme.

Henry Wadsworth Longfellow wrote:
There was a little girl,
Who had a little curl,
Right in the middle of her forehead.
When she was good,
She was very good indeed,
But when she was bad she was horrid.

If you're lucky (i.e., if you're installing Acronis software to a perfectly clean new system with no leftovers from previous installations and no hardware components except those that Acronis happens to possess in its own limited testing labs) it's actually possible to end up with a trouble-free result -- or almost trouble-free other than a few annoying issues with its handling of configuration and task settings. They're not very good at data managment either. And the less said about their newly introduced online "product activation" interactions, the better.

Otherwise, you pays your money and takes your chances on their highly erratic installer package handling of system takeover methodologies that alter your OS/HAL's normal control of storage devices -- or attempt to do so in an utterly incompetent manner taking no account whatever of other filter services and drivers that may already be present, including their own derivative OEM offshoots. And, even if you only did a trial installation, don't expect you can avoid that issue with normal uninstalls of their applications. They leave all kinds of junk behind in your registry and on your hard drive, the former in particular being an open invitation to any number of future disasters.

The only wonder is that there aren't more blue screen death traps reported, but I suppose it's not easy to report anything here with a totally crashed and locked-up computer unless you have a spare and/or a highly recommended pre-install rescue backup. Installing or "upgrading" Acronis software without one is like Russian roulette with the chambers half full.

You can always download the latest version by going to acronis.com, clicking on User Login and logging in, and going the clicking on Get Updates.

Tom Kumpf wrote:

. . . The new process does not allow me to download (I don't think) so I don't know which build it is. . .

Thanks. That occurred to me too and I've done that.

It was in fact build 6131.

Still reluctant to retry. When I have time to commit to a full backup and restore, I may.

and don't forget to use msconfig, jsut in case -- it might help, it can't hurt. ;)

good luck