locked
Needed to Reinstall Vista Ultimate - Stops Working After Numerous Updates with "An Unauthorized Change Was Made ..." Error: 0xC004D401 RRS feed

  • Question

  • So I needed to reinstall my OEM version of Windows Vista Ultimate on the *same* computer as before.  The only difference is switching harddrives (putting it on my velociraptor instead of old 7600 rpm HD that is failing).

    Have spent 3 days on this now ... It works, then after going through 114 Windows Updates, it eventually fails with the above error message. 

    Most recently, it only failed after installing Avast! (the free one).  But, there were still apparently a few updates left (it said no more updates, then one appeared, installed it, then it said no more, etc. - so I did install Avast, then problems).

    The only other things I installed inbetween Vista install disc and the failure were updated drivers from Gigabyte (my MOBO manufacturer) for sound and chipset. Oh, and I installed an NVIDIA driver for my GPU.

    Whenever I follow the links to fix the problem (http://www.microsoft.com/genuine/) it sends me to a page with "Learn more about genuine Windows" and "Learn more about genuine Office" but that's it.

    Here is the Windows Offical Diagnostic Tool v. 1.9.0027.0 readout:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-F86G2-K6JXB-2T6R4
    Windows Product Key Hash: VKE5yfTqu0CZrEqU0P4dMzoD0XA=
    Windows Product ID: 89587-OEM-7347687-66980
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6000.2.00010100.0.0.001
    ID: {2FBB2ED5-A502-4C87-8182-D8FDEDDA45FD}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000009
    Build lab: 6000.vista_gdr.100218-0019
    TTS Error: M:20110327185909204-
    Validation Diagnostic:
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Win32)
    Default Browser: C:\Program Files (x86)\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{2FBB2ED5-A502-4C87-8182-D8FDEDDA45FD}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6000.2.00010100.0.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-2T6R4</PKey><PID>89587-OEM-7347687-66980</PID><PIDType>3</PIDType><SID>S-1-5-21-2018195008-2303229073-3918777636</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>EP45-DS3L</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>f9</Version><SMBIOSVersion major="2" minor="4"/><Date>20080922000000.000000+000</Date></BIOS><HWID>28333507018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAAIfxAAAAAAAAYWECAID6//+GQAeP0OzLARhDs/4hWdo7Xkl9D+HKpnjtEwgob78BI1OTk7inwQgNkC78VIkGONSC0EumYGFJhid7IPmIgITKmLNv1wD2WLY65D/Vu7dAcQHo/vnSgUhxeIRmQLuAjB8KYuz/H5sgFIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsO1pTz6OzglQsN8g+XeKl/d8GxBpop0WwiuBXa5HXuzs1OU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYQ7P+IVnaO15JfQ/hyqZ4jugGdTzMNDENDx7O098Wu+aZwTYXWGcA292j3qM+ufAneyD5iICEypizb9cA9li2OuQ/1bu3QHEB6P750oFIcXiEZkC7gIwfCmLs/x+bIBSKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDtaU8+js4JULDfIPl3ipf3fBsQaaKdFsIrgV2uR17s7NTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(291, 5) (null): 0xC004D401

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: OgAAAAIABgABAAEAAQABAAAAAgABAAEAln0WyLaHIe6Ysgw15L9GvIQ04l+QWO5q8vRk81LNrFYqhQ==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   GBT     GBTUACPI
      FACP   GBT     GBTUACPI
      HPET   GBT     GBTUACPI
      MCFG   GBT     GBTUACPI
      EUDS   GBT     
      SSDT   PmRef  CpuPm


    HELP? Please. Thanks.

    Sunday, March 27, 2011 11:22 PM

Answers

  • "JOJO11111111" wrote in message news:0938fbc8-4ba0-4688-aeff-6171ddcb8276...

    So I needed to reinstall my OEM version of Windows Vista Ultimate on the *same* computer as before.  The only difference is switching harddrives (putting it on my velociraptor instead of old 7600 rpm HD that is failing).

    Have spent 3 days on this now ... It works, then after going through 114 Windows Updates, it eventually fails with the above error message. 

    Most recently, it only failed after installing Avast! (the free one).  But, there were still apparently a few updates left (it said no more updates, then one appeared, installed it, then it said no more, etc. - so I did install Avast, then problems).

    The only other things I installed inbetween Vista install disc and the failure were updated drivers from Gigabyte (my MOBO manufacturer) for sound and chipset. Oh, and I installed an NVIDIA driver for my GPU.

    Whenever I follow the links to fix the problem (http://www.microsoft.com/genuine/) it sends me to a page with "Learn more about genuine Windows" and "Learn more about genuine Office" but that's it.

    Here is the Windows Offical Diagnostic Tool v. 1.9.0027.0 readout:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-F86G2-K6JXB-2T6R4
    Windows Product Key Hash: VKE5yfTqu0CZrEqU0P4dMzoD0XA=
    Windows Product ID: 89587-OEM-7347687-66980
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6000.2.00010100.0.0.001
    ID: {2FBB2ED5-A502-4C87-8182-D8FDEDDA45FD}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000009
    Build lab: 6000.vista_gdr.100218-0019
    TTS Error: M:20110327185909204-
    Validation Diagnostic:
    Resolution Status: N/A

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(291, 5) (null): 0xC004D401


    HELP? Please. Thanks.


    You haven't yet install either Service Pack 1 or Service Pack 2!
    however - your actual problem is what is known as a Mod-Auth Tamper....
    It appears that Avast is often the culprit in this (or at least associated with the problem), so try uninstalling that first.
     
    Vista is in, what we call a 'Mod-Auth' Tamper state.  There are 2 types of Mod-Auth tampers.
     
    1)    A critical system file was modified On Disk - What this means is that the file, located on the hard drive, was modified in some way. This can be caused by a malicious program (spyware, malware, virus) or by manual file modification (by a user of the system). There is also a very small chance that an Update may fail in mid-update and cause this type of issue. As a safety mechanism, Updates are made so that if they fail, they roll back any updating that was done before the failure, but there is an off-chance that the roll back did not occur.
     
     
    2)    A critical system file was modified In Memory - What this means is the file itself (on the hard drive) is un-modified, but the code, from that file, running in the system, was modified in some way and is caused by a running program that is incompatible with Vista.
     
     
     
      Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, we know that your issue is an In Memory Mod-Auth and therefore caused by an incompatible program. This means there is a program install and Running that is trying to access parts of the OS that Vista does not allow, which by definition, means it is incompatible with Vista.
     
    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).
     
     
      In addition to why a Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth event. There is a Service that runs in Vista that detects a Tamper to a Critical System file. But this Service runs randomly, so if you were to install an incompatible program and run it, Vista (most likely) would not immediately enter a Mod-Auth  State and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista detects the Mod-Auth, you know that the program that is causing the Mod-Auth, is currently running.
     
     
     
       Below I have provided a number of steps to help you identify the program that is causing the tamper:
     
      First, go to http://support.microsoft..com/kb/931699/ and confirm that you do not have any of the programs known to cause this type of issue.
     
      Second, in your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch numbers: M:20110327185909204- This is the Tamper Time Stamp and it breaks down like this:
     
        (year)  (month) (day) (time in 24format) (millisecond)
    M:2011     03        27           1859                  09204-
     
     
     

    Now that you know the time of the tamper, you can now try to connect that time with a program.
     
    1)    Login to Vista and select the option that launches an Internet Browser
     
    2)    Type into the browser address bar: %windir%\system32\perfmon.msc and hit Enter
     
    3)    When asked if you want to Open or Save this file, select Open
     
    4)     In the left hand panel, click Reliability Monitor
     
    5)    Click on the “System Stability Chart” above the date 27th March 
     
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 27th March "
     
    7)    Look for any program that shows "Application Install" in the 'Activity' column.
     
    8)    Since the process that detects Tampers runs randomly, it can take up to 3 days for the process to detect the tamper and set Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 24-26 March  (or around the date the issue first occurred)
     
      This could tell you what programs were installed on or around the Tamper date and should help you narrow down the possible programs that could be causing the issue. Unfortunately, if you installed the program at some time in the past, but didn’t run it till now, this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting this issues.
     
     
     
    Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029
     
    Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.
     
    PC Safety:
     
     
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, March 28, 2011 8:23 AM
    Moderator

All replies

  • What I've tried:

    Everything I can find on the net including:

    restarting Licensing system app

    trying to manually install some update (it says its already done)

    searching the web forever ... i can't even get to the telephone verification page.  HELP???

    Sunday, March 27, 2011 11:26 PM
  • OK, I got sick of waiting so shut down my computer.  I noticed the little windows symbol on my shutdown button so used that (the one that means there are more updates to install).  It said it was installing 1/1.

    Now, when I try to logon I get a new error message:

    Unexpected Error:  0xC004F055

    The [something] is reporting that the base SKU is not available.

    I note that my START button now is not accessible.  All I can get is an IE window to open.

    Help *would* be appreciated.  Thank you.

    Monday, March 28, 2011 1:16 AM
  • "JOJO11111111" wrote in message news:0938fbc8-4ba0-4688-aeff-6171ddcb8276...

    So I needed to reinstall my OEM version of Windows Vista Ultimate on the *same* computer as before.  The only difference is switching harddrives (putting it on my velociraptor instead of old 7600 rpm HD that is failing).

    Have spent 3 days on this now ... It works, then after going through 114 Windows Updates, it eventually fails with the above error message. 

    Most recently, it only failed after installing Avast! (the free one).  But, there were still apparently a few updates left (it said no more updates, then one appeared, installed it, then it said no more, etc. - so I did install Avast, then problems).

    The only other things I installed inbetween Vista install disc and the failure were updated drivers from Gigabyte (my MOBO manufacturer) for sound and chipset. Oh, and I installed an NVIDIA driver for my GPU.

    Whenever I follow the links to fix the problem (http://www.microsoft.com/genuine/) it sends me to a page with "Learn more about genuine Windows" and "Learn more about genuine Office" but that's it.

    Here is the Windows Offical Diagnostic Tool v. 1.9.0027.0 readout:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-F86G2-K6JXB-2T6R4
    Windows Product Key Hash: VKE5yfTqu0CZrEqU0P4dMzoD0XA=
    Windows Product ID: 89587-OEM-7347687-66980
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6000.2.00010100.0.0.001
    ID: {2FBB2ED5-A502-4C87-8182-D8FDEDDA45FD}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000009
    Build lab: 6000.vista_gdr.100218-0019
    TTS Error: M:20110327185909204-
    Validation Diagnostic:
    Resolution Status: N/A

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(291, 5) (null): 0xC004D401


    HELP? Please. Thanks.


    You haven't yet install either Service Pack 1 or Service Pack 2!
    however - your actual problem is what is known as a Mod-Auth Tamper....
    It appears that Avast is often the culprit in this (or at least associated with the problem), so try uninstalling that first.
     
    Vista is in, what we call a 'Mod-Auth' Tamper state.  There are 2 types of Mod-Auth tampers.
     
    1)    A critical system file was modified On Disk - What this means is that the file, located on the hard drive, was modified in some way. This can be caused by a malicious program (spyware, malware, virus) or by manual file modification (by a user of the system). There is also a very small chance that an Update may fail in mid-update and cause this type of issue. As a safety mechanism, Updates are made so that if they fail, they roll back any updating that was done before the failure, but there is an off-chance that the roll back did not occur.
     
     
    2)    A critical system file was modified In Memory - What this means is the file itself (on the hard drive) is un-modified, but the code, from that file, running in the system, was modified in some way and is caused by a running program that is incompatible with Vista.
     
     
     
      Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, we know that your issue is an In Memory Mod-Auth and therefore caused by an incompatible program. This means there is a program install and Running that is trying to access parts of the OS that Vista does not allow, which by definition, means it is incompatible with Vista.
     
    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).
     
     
      In addition to why a Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth event. There is a Service that runs in Vista that detects a Tamper to a Critical System file. But this Service runs randomly, so if you were to install an incompatible program and run it, Vista (most likely) would not immediately enter a Mod-Auth  State and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista detects the Mod-Auth, you know that the program that is causing the Mod-Auth, is currently running.
     
     
     
       Below I have provided a number of steps to help you identify the program that is causing the tamper:
     
      First, go to http://support.microsoft..com/kb/931699/ and confirm that you do not have any of the programs known to cause this type of issue.
     
      Second, in your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch numbers: M:20110327185909204- This is the Tamper Time Stamp and it breaks down like this:
     
        (year)  (month) (day) (time in 24format) (millisecond)
    M:2011     03        27           1859                  09204-
     
     
     

    Now that you know the time of the tamper, you can now try to connect that time with a program.
     
    1)    Login to Vista and select the option that launches an Internet Browser
     
    2)    Type into the browser address bar: %windir%\system32\perfmon.msc and hit Enter
     
    3)    When asked if you want to Open or Save this file, select Open
     
    4)     In the left hand panel, click Reliability Monitor
     
    5)    Click on the “System Stability Chart” above the date 27th March 
     
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 27th March "
     
    7)    Look for any program that shows "Application Install" in the 'Activity' column.
     
    8)    Since the process that detects Tampers runs randomly, it can take up to 3 days for the process to detect the tamper and set Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 24-26 March  (or around the date the issue first occurred)
     
      This could tell you what programs were installed on or around the Tamper date and should help you narrow down the possible programs that could be causing the issue. Unfortunately, if you installed the program at some time in the past, but didn’t run it till now, this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting this issues.
     
     
     
    Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029
     
    Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.
     
    PC Safety:
     
     
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, March 28, 2011 8:23 AM
    Moderator
  • Hi Noel:

    Thank you very much for your prompt response.  It is appreciated.

    I had found the above recommendations and "mod auth" problem from a similar thread on these boards, and so I logged in in Safe Mode (it will let me do things in safe mode; in normal mode it locks the whole computer up and I can only get to a browser) and I uninstalled all non-MS software that I could, including Avast.  Notably, my Gigabyte drivers and NVIDIA driver were not listed.  I was also unable to uninstall Adobe's products, receiving an error message about "Microsoft Installation Service" is not running or such.

    Regardless, I uninstalled what I could and rebooted but the problem persists.

    At this point, I believe I will simply try (for a 3rd time) a clean boot and let the software autoupdate.  This time, I will not install ANYTHING until I'm 100% sure that I've gotten through SP2. ... (which was what I was trying to do last time - unsure why it said I had all available updates but then kept coming back with another, then another, etc.)

    Bonus Question:  Is there any way to streamline the update process by downloading to a disk or such the updates so that if I have to do this a 4th time its a bit faster?

    Any other pointers as I embark on what is literally another full evening project (likely 2) on how to streamline this process?

    Many thanks again for your assistance.

    Monday, March 28, 2011 1:30 PM
  • "JOJO11111111" wrote in message news:4bcc79f3-22cd-4304-893e-263949634509...

    Hi Noel:

    Thank you very much for your prompt response.  It is appreciated.

    I had found the above recommendations and "mod auth" problem from a similar thread on these boards, and so I logged in in Safe Mode (it will let me do things in safe mode; in normal mode it locks the whole computer up and I can only get to a browser) and I uninstalled all non-MS software that I could, including Avast.  Notably, my Gigabyte drivers and NVIDIA driver were not listed.  I was also unable to uninstall Adobe's products, receiving an error message about "Microsoft Installation Service" is not running or such.

    Regardless, I uninstalled what I could and rebooted but the problem persists.

    At this point, I believe I will simply try (for a 3rd time) a clean boot and let the software autoupdate.  This time, I will not install ANYTHING until I'm 100% sure that I've gotten through SP2. ... (which was what I was trying to do last time - unsure why it said I had all available updates but then kept coming back with another, then another, etc.)

    Bonus Question:  Is there any way to streamline the update process by downloading to a disk or such the updates so that if I have to do this a 4th time its a bit faster?

    Any other pointers as I embark on what is literally another full evening project (likely 2) on how to streamline this process?

    Many thanks again for your assistance.


    You can download the SP1 and SP2 install packages as standalone installers - you need both, for Vista.
    SP1
     
    SP2
     
    Install the OS
    complete the install - do NOT activate!
    Reboot twice, leaving at least 10 minutes between each reboot.
    Install Chipset drivers if required from CD/USB stick. (do not install anything else at this stage) and reboot.
    Install SP1 from CD/USB stick
    allow 10 mins after final reboot, then reboot again.
    Install SP2 from CD/USB stick
    allow 10 mins then reboot
    go to Windows Update and install all High Priority updates.
    then install your drivers, etc. (unless you have to install any earlier to be able to connect), then the AV.
     
    Installing the AV last reduces the time taken for installing the SP's noticeably, as it doesn't end up scanning every file twice or more
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, March 28, 2011 1:44 PM
    Moderator
  • If I'm using 64 bit Vista Ultimate, I need to use the x64 versions of the Service Packs, right?
    Monday, March 28, 2011 8:55 PM
  • "JOJO11111111" wrote in message news:04b3d4c6-9496-4f58-b2c3-52756c626d37...
    If I'm using 64 bit Vista Ultimate, I need to use the x64 versions of the Service Packs, right?

    Correct - if you get the wrong ones, then they should warn you (big-time!).

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, March 28, 2011 9:46 PM
    Moderator