none
Going around in circles with Validation issue- do i unistall KB3004394 or not? RRS feed

  • Question

  • Hi there

    PC been working with Genuine validation 4 years...until 3 days ago.

    One of the posts (early Dec 2014) says NOT to uninstall KB3004394 as it can cause more issues, but to install the patch 3024777.

    Another post later (24th Dec 2014) says to uninstall the KB3004394.

    Which should I do?

    I copied my diagnostics and had online chat with MS tech who wanted to go into my PC for troubleshooting, but I didn't want this as I think they require payment which I dont want to because their update wrecked my validation. (And I dont want a 3rd party accessing my PC online) The tech confirmed my validation is genuine.

    Tried a system restore that wouldn't work as there is "corrupted files"

    Please advise if i should uninstall the KB update, or just update the patch 3024777 ????

    Many thanks.

    PS If MS know about this issue, why don't they direct me straight to the patch? (Which I asked about)

    Sunday, January 4, 2015 3:21 AM

Answers

  • If you have installed KB3004394, the recommendation is to use KB3024777 to do the uninstall if possible.

    If not, then uninstall using the Installed Updates listing.


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    • Marked as answer by KitKat1000 Saturday, January 10, 2015 4:51 AM
    Sunday, January 4, 2015 9:18 PM
    Moderator
  • 24777 is only offered where 4394 is actually installed.

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    • Marked as answer by KitKat1000 Saturday, January 10, 2015 4:51 AM
    Monday, January 5, 2015 6:38 AM
    Moderator

All replies

  • MGA Diagnostic Report is Required:

    To properly analyze and solve problems with Activation and Validation, we need to see a full copy of the diagnostic report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )

    Once downloaded, run the tool.
    Click on the Continue button, after a short time, the Continue button will change to a Copy button.
    Click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your post.

    Carey Frisch

    Sunday, January 4, 2015 4:55 AM
    Moderator
  • If you have installed KB3004394, the recommendation is to use KB3024777 to do the uninstall if possible.

    If not, then uninstall using the Installed Updates listing.


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    • Marked as answer by KitKat1000 Saturday, January 10, 2015 4:51 AM
    Sunday, January 4, 2015 9:18 PM
    Moderator
  • Hi Noel, thanks I will give that a try, on another PC as I am doing a disk check on my update infected one (4 hrs going on still)

    Managed to delete the rouge update from this PC before install, but weird there was no KB....777 one there as an update, I guess I will manually do it once my infected PC is operational.

    Monday, January 5, 2015 3:30 AM
  • 24777 is only offered where 4394 is actually installed.

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    • Marked as answer by KitKat1000 Saturday, January 10, 2015 4:51 AM
    Monday, January 5, 2015 6:38 AM
    Moderator
  • Okay, well I found it(4394) in update history as "failed", therefore I can't run the 777, makes sense .

    I did a chkdsk and reboots and 2 days OK...now today got another prompt to validate!!!!

    Any other suggestions?

    I tried to cut and paste my diag report and I get an error saying I can't until they verify my account WTF!??

    So I have typed a bit here I thought might be the problem

    File Scan Data-->
    File Mismatch: C:\windows\system32\wat\watadminsvc.exe[7.1.7600.16395], Hr = 0x80092003
    File Mismatch: C:\windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x80092003
    File Mismatch: C:\windows\system32\sppobjs.dll[6.1.7601.17514], Hr = 0x80092003
    File Mismatch: C:\windows\system32\sppc.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\windows\system32\sppwinob.dll[6.1.7601.17514], Hr = 0x80092003
    File Mismatch: C:\windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\windows\system32\slui.exe[6.1.7601.17514], Hr = 0x80092003
    File Mismatch: C:\windows\system32\sppcomapi.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\windows\system32\sppsvc.exe[6.1.7601.17514], Hr = 0x80092003
    File Mismatch: C:\windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x80092003
    File Mismatch: C:\windows\system32\drivers\spldr.sys[6.1.7127.0], Hr = 0x80092003
    File Mismatch: C:\windows\system32\systemcpl.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\windows\system32\user32.dll[6.1.7601.17514], Hr = 0x800b0100


    Tampered File: %systemroot%\system32\sppobjs.dll
    Tampered File: %systemroot%\system32\sppc.dll|sppc.dll.mui
    Tampered File: %systemroot%\system32\sppcext.dll|sppcext.dll.mui
    Tampered File: %systemroot%\system32\sppwinob.dll
    Tampered File: %systemroot%\system32\slc.dll|slc.dll.mui
    Tampered File: %systemroot%\system32\slcext.dll|slcext.dll.mui
    Tampered File: %systemroot%\system32\sppuinotify.dll|sppuinotify.dll.mui
    Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration
    Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui
    Tampered File: %systemroot%\system32\sppcommdlg.dll|sppcommdlg.dll.mui
    Tampered File: %systemroot%\system32\sppsvc.exe|sppsvc.exe.mui
    Tampered File: %systemroot%\system32\drivers\spsys.sys


    • Edited by KitKat1000 Saturday, January 10, 2015 4:51 AM
    Saturday, January 10, 2015 4:38 AM
  • Anyone there?
    Sunday, January 11, 2015 6:22 AM
  • Yeah ;)

    It's better to post the complete report - you can delete the lines with HTTP link in them.

    Having said that, try this...

    This may simply be caused by a bad set of Intel Rapid Storage Technology drivers -  

    Installing the Intel Rapid Storage Drivers

    try downloading and installing them from here - https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2101&DwnldID=22194

    (you want the iata_enu.exe download)

    Once complete, please reboot twice, then post another MGADiag report.   


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Sunday, January 11, 2015 10:12 AM
    Moderator