Skip to main content

Transfer Vista System to new Advanced Format HD

Thread needs solution
Beginner
Posts: 1
Comments: 8

Dear Experts,

I run out of any ideas now. Since two weeks I try to transfer my running Vista System to a new harddrive. But apart from the used procedure I get always awful errors when running the cloned system. Service Windows Search and Cryptographic Service fail to start, I get about 50 erros on boot from these. This will normally result in a non running update service and search is slow.

Source Disk is an Western Digital 250 GB (WD2500BEVS), target disk a Hitachi Travelstar 5K750 750GB (HTS547575A9E384). I know about the 4k-sector issue so I dowloaded and run the Hitachi Align Tool 2.0 from the Hitachi site always after changes to the partitons were made - and before the copied system started first time.

Used Software Acronis True Image Home, V11.0 Build 8.105, started from my Bart PE USB-stick to get the system drive unprotected and unused. Tried original Acronis Rescue Disc once, but it was awful slow and the result has been the same... :-(

Following procdures I tried - all resulting in a running Vista but all with these problems with the services:
- Normal and suggested clone procedure, with and without resizing of partitions
- Backup system partiton to another external drive, restore to new drive, run Align Tool, FixMBR and FixBoot, with and without resizing of partitions
- Backup system partiton to another external drive, restore to new drive, run Align Tool, FixMBR and FixBoot, with and without resizing of partitions, but leaving the rest of the new HD unallocated.

Tried also to fix the problem with the services by some registry hacks - but unsuccessful.

So now I hope that YOU can help me - I have no idea about how to get this working... Thanx!

Tubebend

0 Users found this helpful
Forum Hero
Posts: 82
Comments: 9179

When you restore, are you restoring the disk signature?

Beginner
Posts: 1
Comments: 8

Hi!

Hmm, I think I do not restore the disk ID. Not controlled.

Today morning in the shower (normally best ideas there) I reflected on that perhaps Vista might think it's running in an illegal setting because the HD ID has changed. Perhaps the ID is used for Cryptographic Service which checks the integrity of Vista and programs?

Btw, how to restore the HD signature in ATIH 11.0? I do not remember such an option in the GUI.

Thanks in advance,
Tubebend

PS: Started a sector by sector backup yesterday night - will give it a try and reply result here.

Beginner
Posts: 2
Comments: 13

I am no expert, so take this with two grains of salt. Using the cloning process (Acronis) within windows is usually a bad clone. I use the "Bootable rescue media" and do the clone on the native bootup acronis module. You may have a bad "Bootable Rescue module" so make a new one. I have had great success using this cloning method instead of making backups. It is slow, but I put the module on and start the process at bed time and then finish up in the morning.
If you want to make a clone of a laptop, then purchase a BlacX, plug a laptop 2-1/2 drive into it, plug the USB in and let it run overnight. Works everytime as long as the disk is good. (note: the BlacX is a USB device that you can plug in one or two SATA drives, either 2-1/2 or 3-1/2 drives.

Forum Star
Posts: 27
Comments: 1940

http://support.microsoft.com/kb/2470478

Beginner
Posts: 1
Comments: 8

Hi folks!

Thanks a lot for your suggestions so far.

I'm 99% sure that the image is OK. Tried so many different ways and all result in the same problem with the services. If there would something going wrong with the image, I think not every solution would produce same errors. Nevertheless I'll try the sector-by-sector method to proof the last 1%...

Meanwhile I tried to update my chipset drivers. Installing on an Medion Laptop MD96370, four years old. Updating the drivers result in more errors with cryptographic service and appending. So the update gives an effect, but unfortunately not the wanted one...

kb2470478 describes exactly what happens to my system. Thanks a lot for this hint! "Applications that are built on ESENT and that run on a Windows Vista-based or Windows Server 2008-based computer may not work correctly after the reported physical sector size of the storage device changes" ... "You upgrade your primary storage device that has a 512-byte physical sector size to a storage device that has a 4-KB physical sector size, or vice-versa. And you perform a block-level backup and restore, such as with Windows backup."

I sent a request for this hotfix to MS and will try it next. Reply result here again.

Bye, Tubebend

Edit:
Superb. Now the Hotfix installation fails. Feeling a little angry...

Tubebend

Beginner
Posts: 1
Comments: 8

OK, now things become clearer. Let's resume, also for others having same service errors.

  • I believe in the quality of all the different images I made with ATIH. I found no option to copy also the HD signature in my version 11.0, but I do not think that this adjustment would solve the problem
  • Sector-by-sector backup & restore results in same error scenario
  • Update of the chipset drivers (Intel 945 Express) on the cloned system did not reactivate services, only error pattern changed (more...)
  • Update of the "Intel Rapid Storage Technology Driver" on cloned system did not work for me - message "System does not meet the minimum requirements"
  • KB2470478 explains what happens to ESENT based services and applications when you transfer system drive from 512 byte to 4k advanced format
  • But HotFix "Windows6.0-KB2470478-x86.msu" installation stops with Error code 0xC8000222 when run on cloned system - because of the corrupted update service I want to repair!? This would be a vicious circle!

What about to install the HotFix before starting the system-transfer to a 4k-HDD then? Would be a lot of work (mount old drive, install Hotfix on the source system (also chipset drivers, what do you think?), perform Backup by ATIH, replace HDD, restore backup, run Hitachi align tool on new partitions). Some suggestions on that? Perhaps a shorter way to perform?

Will reply experience again,

Tubebend

PS: Meanwhile I think a fresh Vista installation would have been more convenient in this case...

Forum Star
Posts: 27
Comments: 1940

Is it possible to extract the esent.dll and replace it on the cloned disk? (take care of 32/64 bit versions if your vista is 64 bit)

Beginner
Posts: 1
Comments: 8

@dev-anon:
Sorry, it's too late now to try this manual extraction. Browsing the msu file severals files were shown. I'm currently in state "restore backup" of my to-do list above... Vista is 32bit.

@all:
Is somebody common with the "align" option in diskpart.exe? When I prepared the new disk with two primary partitions I got worried about this option. Finally I choose align=2048 for the first and active primary in hope that I can skip the Hitachi Align Tool procedure. Additionally I defined an offset of 2048k for this partition as well. Will this work?

Thanks in advance

Tubebend

Beginner
Posts: 1
Comments: 8

Dear Experts,

also my procedure #6 is NOT working. I still get the ESENT errors and a non running service Windows Search.

My Vista Home Premium system is (was) a well administrated one with normal applications installed, without bad registry hacks, intensive software testing and so on. Automatic updates active. The Laptop hardware is common. I would call the system ambitious but in general "normal" - it works stable since four years now and it fits my needs. Me I started working with PCs in the DOS 5.0 age on a 80386i, varied experience in adminstrating several OS, hardware configuration, building up own systems, writing batch scripts, installing network and so on. I would not call myself an expert, but I'm also not an novice.

After wasting so much time in this challenge, after extensive research in the web about AFT, partition terminology and disk alignment, ESENT service, reading in forums all over the word, after serveral mount & unmounting of drives, backup & restore, I give up now. What a shame.

It's time to resume that an (Vista)-OS-transfer to a new 4k Advanced Format HDD may not work under certain conditions using Acronis True Image Home and probably other backup software. To anybody reading this - if you try to keep your old operating system working by performing a clone process to a 4k drive you will fail perhaps! It may work on a fresh new installed system. You should keep this in mind when thinking about to use such a drive.

@Acronis Team: Unfortunately users of your software are not warned about the problems which may appear. No guidance, no entry in FAQ. Reading your ads about an easy to use, safe and generous working backup software make me feel cheated. I know that source of errors is located within the Vista system - but it's definitely up to you to inform your users about what may happen when they use your software as recommended - apart from only providing an verified image. This is what I would call "Best Service". It's a shame that your customers have to dive so deep in detail to figure something out about this. Where is your assistance here? Disastrous if someone accepts clearing of source disk when asked by ATIH after the cloning process! This question alone suggest that everything is "no problem".

I can't believe that my system is so special that I'm the only one blindsided by this hazard. How many normal users without administrator background will notice that their system is not proper working after an "easy change" of the HD? What percentage knows just about the existence of the event viewer?

A fresh Vista installation is runnung now. Loaded first 107 updates this morning. No ESENT errors so far.

Tubebend

Beginner
Posts: 1
Comments: 8

Here my last reply to my own thread... :-)

Problem is solved, old system is running now on the new Hitachi 5k750 4k-drive without ESENT errors anymore. Lucky.

Problem persist really in the Intel Rapid Storage Technology driver. When installing the fresh Vista I installed chipset driver set called "Matrix Storage Manager 8.9.0.1023" for the Mobile 965th Express Chipset I own. And here we are - same errors again. But as described above, the installation of the newer "Intel Rapid Storage driver 10.6.0.1022" (IRST) failed with the message "System does not meet the minimum requirements". No RAID available in this lazy Phoenix BIOS. Intel tools response "Everything is up-to-date". Shit.

Somewhere in the web I've read that you need min. version 9.6 or later of this IRST driver. So I looked for exact the lowest needed version 9.6. This installation routine worked also on my system lika a charm, afterwards Vista started without errors. Now feeling a hero I installed the actual version 10.6.0.1002 using the F6 floppy disk set - so no installation routine to beef about system requirements but the newest iastor.sys installed.

The Vista HotFix from above may be as obsolete as the pre-installation of IRST 9.6. But who cares - it's up to the next clueless to figure this out... :-) My step-by-step guide, use at your own risk:

  • Install support.microsoft.com/kb/2470478 on old HDD (maybe obsolete)
  • Check version of (RAID and) AHCI drivers. You'll need at least version 9.6 or later of iastor.sys for Intel chipset. If another Chipset is used check the web for hints which version is needed for AFD. If current driver is older I suggest to update drivers by a manufacturers update utility. Manual driver installation below should be done on cloned system to keep your original one save
  • Perform system backup or clone process as suggested with Acronis True Image or similar. Keep old HDD as additional backup!
  • Restore image to new 4k Advanced Format HDD. If using Acronis True Image Home 11.0 partition will be probably nonaligned afterwards (aligned to Sector 63)
  • Run Align Tool Provided by drive manufacturer. In my case www.hitachigst.com/hdd/support/downloads/AcronisAlignmentTool.exe
  • Open System Recovery Options using Vista/Windows 7 installation DVD, open Command Prompt and rebuild Master Boot Record (MBR) (/FixMbr, /FixBoot) and Boot Configuration Data (BCD), refer to support.microsoft.com/kb/927392/EN-US (maybe obsolete)
  • Start recovered system, check Event Viewer for ESENT entries and several other errors. If none, everything is fine, nothing else to do
  • For Intel chipset and if installation of latest Intel Rapid Storage Technology driver fails run downloadmirror.intel.com/15251/eng/STOR_allOS_9.6.0.1014_PV.exe and restart system
  • Check output in Event Viewer. ESENT messages should not be displayed anymore. Check also Windows Update Service is running. Use e. g. www.hdtune.com/files/hdtune_255.exe to check your new HDD's performance
  • If you like to: Update AHCI driver to last version using Windows Device Manager, manual driver update tab and F6 Floppy Disk driver set for loading prior OS-Installation as source. Look for last driver on manufacturer site, in my case downloadmirror.intel.com/20216/eng/10.6_f6flpy-x86.zip for Intel 965th Express Notebook AHCI chipset
  • Keep your old HD save for a few weeks while verifying stability of the new drive

Additional pending documents:

Cheers, Tubebend

Forum Hero
Posts: 82
Comments: 9179

Thanks for the guide, Tubebend. Nicely done!

Beginner
Posts: 0
Comments: 1

Tubebend, First off.. THANK YOU! Considering the number of days you spent chasing after this, I appreciate the fact that you followed up to the bitter end and posted the fix. That doesn't always happen. I run a small side business fixing PCs here and there for extra income.. I do have 25 years experience (hurts to say that) so I'm no slouch... I have to say, with all that, I smacked myself in the head when I wasted so many hours on the new drive trying to figure out what the issue was with the Windows search service, then the cryptographic, etc, etc.. I too quickly attributed the erors to corruption from the old drive I was replacing.. and THEN decided to throw the old drive in just to see if it was happening before.. DOH! Rub the google belly and voila, I find you.. I was so happy that I wanted to follow on to your wisdom with inputs and my variation, which in no way diminishes what you did but is intended to reinforce it for any others..

Machine: HP Pavilion DV4-1465dx w Vista HP SP2

Old Drive: WDC Blue Scorpio 320Gb

New Drive: WDC Black Scorpio 500Gb

Original imaging was done using Acronis 2011 Home, booted on Acronis Recovery media, Drive clone.. old to new..

Insert 1 day of swearing and research...

Resolution:

Step1: Put old drive back in the machine

Step 2: Installed 2470478 from MS

Step 3: Re-cloned the drive using the same process (booted off Acronis Recovery)

Step 4: Swapped drives

Step 5: Downloaded/Booted ran WDC Alignment tool (note: the tool is by Acronis) Result: Not needed.. I believe that the Acronis cloning software already has the alignment algorithm thereby elminating the need for this step.. Results may vary if you have a different drive manufacturer OR use a different cloning/imaging method.

Step 6: Booted on the new drive... (Issue still present)

Step 7: Downloaded the new Intel Driver and installed... Rebooted

Step 8: Booted on Vista Installation Recovery and issued /FixMBR

Step 9: SUCCESS! Normal operation resumed.

Admittedly, one might think I could have just installed the Intel driver on the 500 and skipped the reimaging, however, in that 1 day of trying to troubleshoot the Windows search service, and everything else.. who knows what might have been bastardized.. So ergo safety first.

Again, I want to express my sincere thanks..  

---- NCSDiver

Beginner
Posts: 1
Comments: 8

Hello NCSDiver,

I'm glad that my small guide helped you to solve your problem - and thanks for your response!

After spending so many hours on this task I was not satisfied by just to have running system. I got many information from the web, surfed several forums and collected finally enough info to solve my problem. Not the last (and most important) one, but nevertheless without these input I would problably still search for a solution.

This is how community works - get and give back. Like you also did with your post.

Cheers, Tubebend

PS: BTW, system still works like a charme. :-)

Forum Member
Posts: 6
Comments: 24

Unfortunately none of this helps me at all. I replaced my old (512 byte sector) drive when it failed and restored to a new 4kb-sector drive (both Western Digital).  I now have the problem described here and no way to go back to the original hd although I have a good image (from the new 4kb. sector drive though!).  This machine is a refurbished laptop so no system discs of any sort--and none available I found out yesterday!

I read all of this thread after I successfully installed IRST which at least allowed catdb to rebuild but I'm still stuck with no windows updates, no search, etc.  When I try to  install Windows6.0-KB2470478-x64 hotfix I get 0xc8000222 error.

First, I agree--Acronis should have let users know about this.

Second, the only image I now have is one made from my current (4kb) hard drive.  If I understand the above correctly, my only chance at the moment is to locate a 512b. -sector drive and restore to it, then go through the procedure above, then image, and then restore to my new drive?????

Of course I'm not at all sure that would work given that the image I would now be using would be one created from the 4kb drive.  Also, I don't have and apparently can't get system discs from either the manufacturer (Gateway) or the refurbisher (Seneca).

Second, is there any other way to fix this.  I really like the laptop in question--very nice large screen for tired eyes like mine!!!

This is awful!

Beginner
Posts: 1
Comments: 8

Hello Jerald,

I never figured out if the described steps above are really all needed or if parts of them are obsolete or can be realized after the restore to the new 4k-drive.

Where exactly your image comes from? Is it one you took from your original drive before it crashed? Then I think it will work to restore this image to another 512k drive, perform the described procedure and restore it again to the new drive. You will like that all your programs and data will still be there.

I understand your message in the way that you have already a running OS on your new drive. Performed by a Windows setup routine? If you have this problems with a fresh installation of Windows all the image stuff will probably not help you anyway!

Hints: When installing the new Windows provide a so called F6 floppy disk set for your chipset and IRST. Load these drivers when asked by the setup routine. This is the way I would go on. Another chance is to update your Windows source disk. Windows Vista and 7 should be 4k-drive-ready, but perhaps you need some hotfixes or service packs for this. Look for the keyword "slipstream" to figure out how to build an already up to date installation disk based on your old one.

Good luck, Tubebend

Forum Member
Posts: 6
Comments: 24

Hello Tubebend,

Tubebend wrote:

Hello Jerald,

I never figured out if the described steps above are really all needed or if parts of them are obsolete or can be realized after the restore to the new 4k-drive.

For me that would be really useful information if anyone knows!

Tubebend wrote:

Where exactly your image comes from? Is it one you took from your original drive before it crashed? Then I think it will work to restore this image to another 512k drive, perform the described procedure and restore it again to the new drive. You will like that all your programs and data will still be there.

No—the image I have is several generations after the move to the new drive.  I don't have the original image—I disposed of the original laptop hard disk which, in any case, had died.

Tubebend wrote:

I understand your message in the way that you have already a running OS on your new drive. Performed by a Windows setup routine? If you have this problems with a fresh installation of Windows all the image stuff will probably not help you anyway!

I know—and I'm not up for buying a new full-retail version of Windows 7 for this machine just so I can try to save everything.

Tubebend wrote:

Hints: When installing the new Windows provide a so called F6 floppy disk set for your chipset and IRST. Load these drivers when asked by the setup routine. This is the way I would go on. Another chance is to update your Windows source disk. Windows Vista and 7 should be 4k-drive-ready, but perhaps you need some hotfixes or service packs for this. Look for the keyword "slipstream" to figure out how to build an already up to date installation disk based on your old one.

Good luck, Tubebend

I'm still wondering if anything really important to the ESSENT error has changed in my current image.  I'm suspicious enough that it might not have that if I could find a 512K-sector hard drive that wouldn't cost me much of anything, I'd put this image on it,check to see whether search and Windows update are working on that restore, and if they are, run through the procedure above, and then try to restore that image to the new 4K-sector drive.  It might be a bust but then again it just might work.  The key is finding a low-cost 512K-sector hard drive to test the theory.

In any case, thanks for the prompt and thoughtful reply!

Forum Member
Posts: 6
Comments: 24

Obviously the key question in terms of whether this approach is worth the effort of trying to find an older SATA drive that can only handle 512-byte sectors is whether the image I have from the new drive could even restore a functional operating system to a drive limited to  512-byte sectors.

Any thoughts on that?

Legend
Posts: 172
Comments: 11125

This link may be of interest.
http://forum.acronis.com/forum/30234#comment-94148

Forum Member
Posts: 6
Comments: 24

Thanks Grover,

While this thread doesn't seem to deal directly with my problem, it does as you suggest, have some potentially interesting implications for it.

I just updated to Acronis 2012 and have the build discussed in this thread so it might be worth doing an image and restore with that although I doubt anything will change.

In any case, thanks for the reply!

I wonder if alignment to sector 63 by itself would produce the ESSENT error problem or if the problem is the result of both the alignment problem and sector size.

Forum Member
Posts: 6
Comments: 24

Tried imaging with 2012, nuking everything including MBR, and restoring, but still can't install the hotfix.

Forum Star
Posts: 88
Comments: 4769

Hello Jerald,

Thank you for your message and welcome to the forum.

We will need to investigate this issue I am afraid and I found your case in our Support system. I am certain that we will be able to provide you with an answer.

I will also follow-up with a private message to provide you a download link for the bootable media that you could not download.

Please let me know if you need additional help.

Thank you.

Beginner
Posts: 0
Comments: 1

This thread is pretty old, but maybe what worked for me might help someone. I've had most of the problems described in this thread, but I managed to get windows update working again after a clone to an advanced format drive. I don't have the Intel RAID chipset driver installed, so that doesn't appear to be the fix (although I did use the Intel Chipset Device Software to install the lastest chipset driver). This hotfix: http://support.microsoft.com/kb/2553708 fixed my problems with Update (no guarantees there aren't other problems I haven't discovered yet), but it's not trivial to install. I used a modified procedure originally from this link: http://answers.microsoft.com/en-us/windows/forum/windows_other-windows_update/windows-7-windows-update-broken-after-disk-clone/586da306-3cdc-4f32-acfc-61c3b140e11e?page=6&tm=1307112299994#footer

Note this is for a Vista 64bit system. You may need to change the procedure for a 32bit system, but the changes should be obvious.
1) D/L the hotfix
2) Run the file and expand into some directory, I'll call it 'dir'
3) in the command shell, do:
cd dir
mkdir msu
expand Windows6.0-KB2553708-x64.msu -F:* msu
cd msu
mkdir cab
expand Windows6.0-KB2553708-x64.cab -F:* cab
4) in windows explorer, Rename esent.dll in C:\Windows\System32\ and C:\Windows\SysWOW64 to esent.dll.old
5) go to dir\msu\cab
5) search for esent.dll
6) In my case, there were 32 bit and 64 bit versions. The 64bit version is identifiable because it's in an *amd64* folder.
7) Copy the 64bit version of esent.dll into the System32 and SysWOW64
8) Reboot
9) Run Windows6.0-KB2553708-x64.msu
10) Reboot

Forum Hero
Posts: 82
Comments: 9179

Thanks for sharing!

Beginner
Posts: 0
Comments: 1

I know this thread is a bit old, but I struggled for days (off and on) with the same problem, and I thought I'd contribute what worked for me in case it would help someone else. My method is largely what others have written here, but there were just enough twists to throw me off and require me to do a bunch of web research, and follow some blind alleys.

Hardware/software situation:
o Vista Home Premium SP2 32-bit
o Lenovo ThinkPad SL500 laptop with 4GB memory and Core 2 Duo P7370 processor
o Original HDD - Hitachi 250GB SATA - not Advanced Format
o Desired new HDD - Western Digital Scorpio Blue 1TB SATA - Advanced Format

What I did...

1. In the 250 GB HDD, I installed the hotfix rollup KB2553708. http://social.technet.microsoft.com/Forums/en/itprovistahardware/thread/32fe71df-35a6-4294-a1d6-ba2a59228348. It is supposed to enable Vista to use Advanced Format drives, and contains a newer version of ESENT.dll which is what seems to cause all the trouble. It needs to be installed while on the non-AFD drive, before cloning to the AFD drive.

2. I cloned the 250GB drive to the 1TB drive. I used Acronis True Image WD Edition, available free from the Western Digital website for use with WD drives. This version of Acronis is documented as being able to automatically align partitions to 4KB boundaries, as required by AFD drives. Other HDD manufacturers may provide similar utilities. I did the cloning in a Windows 7 desktop, by connecting each drive to spare SATA ports and spare SATA power connectors. (Actually, since this desktop has a front-mounted 2.5 inch hot-swap bay, I used that for one of the drives.) After this step, the 1TB AFD drive should have the new ESENT.dll, and it did, as verified by version numbers - but the problem was still there.

3. I checked to see what version of the SATA driver I had. Device Manager | IDE ATA/ATAPI controllers | Intel(R) ICH9M-E/M SATA AHCI Controller | Driver Details. I had Matrix Storage Manager (MSM) version 8.3 (if I remember correctly).

4. In the 1TB Vista clone, I installed the Intel Matrix Storage Manager (MSM) Driver 8.8 from the Lenovo Support site (the most recent SATA driver Lenovo lists for the SL500) and rebooted - but the problem was still there.
5. In the 1TB Vista clone, I installed the Matrix Storage Manager (MSM) Driver 8.9 from the Intel drivers site (the most recent MSM driver Intel lists) and rebooted - but the problem was still there. (I did the in-Windows installation, not the floppy installation.)

6. I updated the SL500's BIOS from the Lenovo Support site from v1.19 to v1.30 - but the problem was still there. (I don't really have any evidence that the BIOS update was needed, but I was running out of ideas.)

7. In the 1TB Vista clone, I did the Intel Rapid Storage Technology (RST) Driver 11.2.0.1006 from the Intel site - PROBLEM SOLVED!!! (I did the in-Windows installation, not the floppy installation.) The Intel search page for this is:

http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=software+products&ProductLine=Chipset+Software&ProductProduct=Intel%c2%ae+Rapid+Storage+Technology+(Intel%c2%ae+RST)

The list of RST and MSM drivers for Vista was here:

http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=software+products&ProductLine=Chipset+Software&ProductProduct=Intel%c2%ae+Rapid+Storage+Technology+(Intel%c2%ae+RST)

The RST 11.2 page was here:

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2101&DwnldID=21730&ProductFamily=software+products&ProductLine=Chipset+Software&ProductProduct=Intel%c2%ae+Rapid+Storage+Technology+(Intel%c2%ae+RST)&lang=eng

The specific file I downloaded was RST version 11.2.0.1006 dated 06/07/2012, named iata_enu.exe.
---------------
The reason I left this RST driver update to the end: My SL500 contained an Intel Matrix Storage Manager driver, whereas sites like this talked about updating their Intel Rapid Storage Technology driver. I assumed they were two different things, intended for different hardware and/or software configurations. I figured that if there was an RST driver version that had been updated for AFD's, there might also be an MSM driver version similarly updated. Therefore I spent too much time trying to find an MSM driver that would work.

Eventually, I read on the Intel site that the highest version of MSM was 9.5, and for 9.6 they renamed the product to RST. So MSM and RST really were the same thing.

Many sources on the internet, including the Intel site, referenced the Intel RST 9.6 driver as being needed. I had a hard time finding this version of the driver, and when I finally found it, it was documented as being for Intel desktop boards.

The only version of the RST driver that Intel showed for Vista is 11.2. However, RST Version 11.2 is documented in the Readme as requiring one of the following processors: Intel(R) vPro, Intel(R) Celeron, Intel(R) Pentium. My Lenovo SL500 doesn't have any of these (as far as I understand) - it has an Intel Core 2 Duo P7370 processor. However, my ICH9M-E/M SATA AHCI Controller was specifically listed as being supported.

So, I decided to try the RST 11.2. I figured that if it didn't work, I could always clone the 1TB drive again from the 250GB drive, and try something else.

References that helped the most were:

http://forum.acronis.com/forum/25558 (this article)

http://social.technet.microsoft.com/Forums/en/itprovistahardware/thread/32fe71df-35a6-4294-a1d6-ba2a59228348

http://forums.seagate.com/t5/Momentus-XT-Momentus-Momentus/Vista-problems-after-cloning-a-ST9320421AS-to-ST9750420AS/td-p/142967

http://support.microsoft.com/kb/2470478

http://support.microsoft.com/kb/2553708/en-us

To summarize, if I had to do it again, I would try this sequence:
1. In the 250GB drive, install hotfix KB2553708.
2. Clone the 250GB drive to the 1TB drive.
3. In the 1TB drive, install Intel RST 11.2 SATA driver.
4. Only if things still don't work, update the BIOS.

Beginner
Posts: 0
Comments: 1

Dear folks,

in short words: You will need at least Intel Rapid Storage Technology Driver version 9.6. It does not matter where to get or how to install, with a RST driver version lower than 9.6 you will not get Vista working with update service on an AF drive. Don't waste your time, just clone your disk, run an align tool and install the right driver following the guides above. Then it is a question of spending hours - not weeks as for me...

I'm glad that this thread helps others around. This has been my intension. Success!

Cheers,

Tubebend (with a still running system :-)

Beginner
Posts: 0
Comments: 1

Hello, Tubebend,

No matter what this topic is quite old, I want to say a special thank to YOU, because your solution helped me to solve my problem. Your post #10 is real manual for cloning non-AF to AF disks for Vista OS. And, I have to emphasize that essential problem is Intel RST driver. Before "final victory" I made all the other updates (Microsoft Hotfix, uninstall old Intel driver, install new Intel Chipset Driver, Intel Matrix Driver etc... All of them I chose carefully, looking for for my chipset and operation system. Nothing helps. Finally, in desperation, I've just clicked on your link for Intel RST ver 9.6 and installed it. Full success! Even without aligning (align tool showed that all is OK), and without FixMBR, FixBOOT etc...

Beginner
Posts: 0
Comments: 1

It worked !

Hi, folks,
This is yet another occurence of a user expressing his gratitude to the contributors to this very useful set of posts and very particularly to Tubebend whose thorough research and clear explanations guided me to success thru the conversion process to AF.
This topic might become increasingly popular as the Vista-based PC's equipped with non-AF drives are ageing and increasingly susceptible to HDD failures while at the same time procuring a non-AF drive for replacement is getting difficult and, when feasible, highly cost-ineffective.
For the record, my configuration is a Sony VGN-FW21E, initially equipped with a 320GB Toshiba MK3252GSX and an ICH9M-E/M based chipset, and running Vista Home Premium SP2 32-bit.
After a disk crash, the disc appeared beyond repair, so I bought an HGST Travelstar 7K1000 (HGST HTS 721010A9E630) as a replacement, unaware of the Advanced Format issue.
I began by salvaging most of my personal files from the (severely) crashed disk using the recovery DVD to get to command prompt and then using Testdisk-6.14 (great program !!).
After replacing the failed drive with the new one, attempt to restore the system with the recovery DVDs, concluded with an "Error 333" resulting from the unsupported AF format.
With better understanding at this point, I might have tried using Intel's so-called F6 floppy utility to update the chipset driver early in the recovery process, thus providing Intel Rapid Storage Technology support (version 9.6.0 or higher) during recovery. I didn't, and cannot vouch for this to be a working solution, but given the opportunity, I would certainly try it.
I still had to include Intel RST, but did it the long way :
1- replaced the HDD with a 2.5" non AF disc extracted from an old Iomega external USB drive that I was lucky to own, and performed recovery to it. Recovery to a smaller drive (250GB instead of 320) worked fine. Using Wmic at the command prompt proved useful in showing the partitions were aligned to a multiple of 8 sectors on the non -AF disc (this becomes a benefit after faithful cloning to the AF disc)
2- brought Vista back to the latest update status (had to batch updates by groups of consecutive issue dates, otherwise some would not install)
3- found it worth the trouble to save the image of the Vista partition using a cloning utility (but this is an optional step) BEFORE the tricky changes to Vista
4- then applied hotfix KB2470478 (may be KB2553708 is an improved alternative or beneficial addition, but I missed it and it was ignored)
5- installed Intel RST 9.6 using Intel(R) Chipset Software Installation Utility a.k.a Intel Chipset Device Software (the version of iaStor in windows\drivers\INF directory remains unchanged but checking version via the "Driver details" in the "Device Manager" of the Control Panel, as per Intel readme file accompanying the download, shows the update was indeed performed).
6- Cloned the full disc (or rather saved disk image and loaded it back to the new drive).
Alignment was preserved and was not an issue. It is a pity HGST no longer provides a free alignement nor , more importantly, a free cloning tool for their customers on their site, but free tools exist.
7- At this point, right after cloning, the disc would not boot but bootinfo was clearly reported as being the problem.
8- Booting again with the recovery DVDs and selecting the "Repair Vista", then the "Repair boot" options from the menu did what could otherwise have been explicitely requested using bootrec /FixMBR, bootrec /FixBoot, etc. Boot repair completed successfully.
After that, Vista booted smoothly, HDtune showed improved disk performance, the Event Viewer was not reporting anything worrying, and Windows Update was working fine. This is, therefore, considered success and will indeed be, unless something new shows up to prove me wrong in the coming weeks.
Thanks to all. Hope this helps too.

Beginner
Posts: 0
Comments: 1

Thank you!!!! I know it's been years since you found the fix for this, and I am so happy you did! The 9.6 version of IRST is what saved me.

I cloned a WD 160 TB HDD, original to my 2008 Vista machine to a WD 1 TB HDD, circa 2014. The newer AF drive worked just fine until I went to search for something, and that's when I found it: No Windows Search b/c the Index was not running and No Windows Update, either. I have worked on this off and on for weeks and then I found your post. It worked perfectly!!

1 - Install the Intel Chipset Software Installation utility
2 - Install the Intel Driver Update
3 - Install the Rapid Storage Technology version 9.6 (mine was named: STOR_allOS_9.6.0.1014_PV)

Note, the first two can be found searching the Intel site, and the 9.6 version can be found with a Google Search.

I did install the Intel Matrix Storage Manager before the RST 9.6, but it didn't help. I don't know if it facilitated an easy installation of RST 9.6, though. The Hotfix from Microsoft was not helpful and neither was the WD Align Tool, both of which I also tried. I used the WD free version of Acronis to clone the drive, which seems to have worked just fine, minus the Search & Update issues.

I hope you've been enjoying your HDD for the past few years and want to thank you again...You are a life-saver!!!!!!