[SOLVED] Issue with Server 2012R2

I

itguy540

Active member
Joined
Jan 19, 2024
Posts
29
Quick question - Attached is setupapi.dev.log from another Windows host (running Server 2012 R2) that is having a similar issue. I looked at this log file and I see the same/similar failure errors for the atapi.sys driver.

Would the same "fixlist.txt" (run with PsExec) work for this server as well?

Do you happen to know what causes this issue (both Windows hosts are VMs, if that matters) or is this just a coincidence?
 

Attachments

Hi,

I have moved your post from this thread to a new one, since it has to due with server 2012 and not 2016! This just to avoid any confusions.
 
Please do the same as in the other thread to look at the Services hive. Then I can compare some things with a Server 2012 VM here.

Export registry key as hive file.
  • Open the Start menu of Windows and type CMD.
  • When you see Command Prompt on the list, select the option Run as administrator.
  • Copy and paste the following command into the command prompt and press enter.
Code: 
reg save "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services" "%userprofile%\Desktop\Services.hiv"
  • Once done, a file will appear on your desktop, called Services.hiv.
  • ZIP this file and attach it to your next reply.
 
Here's the fix for this 2012 R2 Server.

Please follow these instructions to run the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool with system privileges.

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download PsExec from Microsoft Sysinternals to your desktop.
  • Unzip PsTools.zip to its own directory on the system drive, for example: C:\Tools\PsTools
  • Navigate in an elevated command prompt to the PsTools directory: cd C:\Tools\PsTools.
  • Now copy and paste the following command into the command prompt and press enter. Click on the Agree button when the licence agreement of PsExec appears.
  • Note: Ensure that both FRST64.exe and the Fixlist.txt file are on your desktop! Otherwise you'll need to ammend the command to the right location.
    Code: 
    psexec -i -d -s "%userprofile%\desktop\FRST64.exe"
  • FRST will make a new backup of the registry first, please wait until this process is completed.
  • Ensure the provided Fixlist.txt is in the same location as FRST64.exe and then press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Rich (BB code): 
Registry ====> The operation completed successfully.

Great! Please reboot this server and attempt to update and post he result. If it fails attach a new copy of the CBS logs and the Setupapi.dev.log file.
 
I rebooted, installed the updates, rebooted again and it unfortunately rolled back the updates/changes again.

Attached are the new set of logs (from the Server 2012 host)
 

Attachments

Hi,

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download PsExec from Microsoft Sysinternals to your desktop.
  • Unzip PsTools.zip to its own directory on the system drive, for example: C:\Tools\PsTools
  • Navigate in an elevated command prompt to the PsTools directory: cd C:\Tools\PsTools.
  • Now copy and paste the following command into the command prompt and press enter. Click on the Agree button when the licence agreement of PsExec appears.
  • Note: Ensure that both FRST64.exe and the Fixlist.txt file are on your desktop! Otherwise you'll need to ammend the command to the right location.
    Code: 
    psexec -i -d -s "%userprofile%\desktop\FRST64.exe"
  • FRST will make a new backup of the registry first, please wait until this process is completed.
  • Ensure the provided Fixlist.txt is in the same location as FRST64.exe and then press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Here's the next fix.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download PsExec from Microsoft Sysinternals to your desktop.
  • Unzip PsTools.zip to its own directory on the system drive, for example: C:\Tools\PsTools
  • Navigate in an elevated command prompt to the PsTools directory: cd C:\Tools\PsTools.
  • Now copy and paste the following command into the command prompt and press enter. Click on the Agree button when the licence agreement of PsExec appears.
  • Note: Ensure that both FRST64.exe and the Fixlist.txt file are on your desktop! Otherwise you'll need to ammend the command to the right location.
    Code: 
    psexec -i -d -s "%userprofile%\desktop\FRST64.exe"
  • FRST will make a new backup of the registry first, please wait until this process is completed.
  • Ensure the provided Fixlist.txt is in the same location as FRST64.exe and then press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Hi,

You're welcome. Glad everything is up and running again, I will mark this thread as solved... (y)
 
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