[SOLVED] Windows 2012 R2 - KB2919355 always fails with 0x8007000d

KeithPooleCW

KeithPooleCW

Member
Joined
Mar 13, 2019
Posts
21
I have a Server 2012 R2 Hyper-V host with exactly the exact issue (CBS log extract attached) of [SOLVED] - Windows 8.1 - KB2919355 always fails with 0x8007000d.

I've tried the usual DISM, SFC, WU component cleanup, etc, manual MSU install, etc, to no avail. This appears to have been a result of OS corruption after a UPS failure, and is the seemingly only corruption, but driving me mental.

As the log shows, same acpi.inf driver install failure, then rollback. Same KB too! Interestingly this server was up to date prior to the recent power issue, then had DISM and SFC performed after the corruption, and then this is just the one update left that I guess was 'repaired' but is possibly in an inconsistent state.

Windows Update actually shows the install as a success each time for some reason, and two of the ~12 attempts I've done in the last month have resulted in a hal.dll BSOD too.

CBS log for the reboot after an attempted install here: server cbs.txt.

Thanks in advance
-KP
 
Hello and welcome!

I would suggest that you do try the fix I have provided in that thread as it appears your driver store may be corrupt.

Though, I would advise you to have a solid backup just as a fallback plan.
 
Hey

That all sounds well and good, but
"C:\Windows\System32\DriverStore\drvindex.dat" => not found
"C:\Windows\System32\DriverStore\INFCACHE.0" => not found
"C:\Windows\System32\DriverStore\INFCACHE.1" => not found
"C:\Windows\System32\DriverStore\INFCACHE.2" => not found
"C:\Windows\System32\DriverStore\OLDCACHE.000" => not found
"C:\Windows\System32\DriverStore\infpub.dat" => not found
"C:\Windows\System32\DriverStore\infstor.dat" => not found
"C:\Windows\System32\DriverStore\infstrng.dat" => not found

Thoughts? Note Server 2012 R2 Standard x64.

Thnx.
-KP
 
This must've fallen through the cracks! My apologies!

Please attempt the install again and attach CBS.log and C:\Windows\Inf\setupapi.dev.log after it fails again.
 
Hey all good it happens!

Scheduled update to install in 4 hours, reboot in 8. Will send the logs tomorrow morning (approx 15 hours)
 
Driver version 6.3.9600.16384 date 21/06/2006. Search online; Windows has determined that the driver software for your device is up to date.
 
SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

Hi,

Softwaremaniac is currently very busy with real-life obligations... It's ok for you if I try to help on this problem?


Open the Command Prompt, and execute this:
reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ACPI /s

Please copy & paste the result to the topic.
 
Hey no worries at all!


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ACPI
ImagePath REG_SZ System32\Drivers\ACPI.sys
Type REG_DWORD 0x1
Start REG_DWORD 0x0
ErrorControl REG_DWORD 0x3
DisplayName REG_SZ Microsoft ACPI Driver
Owners REG_MULTI_SZ acpi.inf
Tag REG_DWORD 0x2
Group REG_SZ Core

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ACPI\Parameters
WHEAOSCImplemented REG_BINARY 01000000
APEIOSCGranted REG_BINARY 01000000

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ACPI\Enum
0 REG_SZ ACPI_HAL\PNP0C08\0
Count REG_DWORD 0x1
NextInstance REG_DWORD 0x1
 
Hi,

Lets do this... for the changes to take effect the server needs a reboot.


Farbar Recovery Scan Fix

!!! WARNING !!! The following fix is only relevant for this system and no other, running the script on another computer will not work and may cause problems...

  • Download FRST or FRST x64 and save it to the Desktop.
    (Please pick the version that matches your operating system's bit type. If you don't know which version matches your system, try FRST if it say that is not compatible with your OS you have to use FRST64
  • Download the file attached and save it to the Desktop as fixlist.txt
    (It's important that both files, FRST or FRST64 and fixlist.txt are in the same location or the fix will not work!)
  • Execute FRST/FRST64 right click on the icon
    FRST.gif
    and choose Run as Administrator. Make sure all other windows are closed.
    FRST_Fix.png
  • Press the Fix button just once and Wait. After the fix the system needs to restart if the tool does not request it please Restart the computer.
  • The tool will make a log (Fixlog.txt) on the same location as FRST/FRST64 please post it in your next reply.

After the reboot try to update.
 

Attachments

Thanks - applied now and scheduled reboot for tonight.

So just DisplayName value change?

Will see how the update goes tomorrow.
 
Ah yeah I see. Missed that.

Applied, rebooted, BSOD, rebooted again and applied update. Next reboot happening in 6 hours (maint Window)
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top