Skip to main content

Windows Server 2008 R2 always boots in recovery mode

If you are facing below Issues : 
- You faced the Windows Server 2008 R2 Clean boot issue
- Windows Server 2008 R2 starts in recovery mode
- After installing windows updates on Windows server 2008 R2 system goes in recovery mode after reboot
- Safe mode also doesn't work in above case and get stuck at classpnp.sys

Then this is the solution for all above:

1. Boot into Windows Recovery Mode
2. Open Command Prompt
3. Type:

sfc /SCANNOW /OFFBOOTDIR=C:\  /OFFWINDIR=C:\Windows

4. Goto following location :

C:\Windows\winsxs\
 Check out for pending.xml file.
If it is present, then DELETE it.

5. Reboot the system.

6. Select normal boot mode. 

You have done it!

Comments

  1. Wow this was a great fix since I was seeing the exact problem with the server only booting sometimes. Thank you!!

    ReplyDelete
  2. Thats Great... I am glad that the solution helped you.

    ReplyDelete
  3. Hi, i try this fix but get: the windows resource protection could not start the repair service

    ReplyDelete

Post a Comment

Popular posts from this blog

Solved | SendGrid SSL CERTIFICATE_VERIFY_FAILED certificate verify failed | self signed certificate in certificate chain

Error :   PS C:\Ashish> & "C:/Program Files/Python39/python.exe" c:/Folder/SendEmail.py Traceback (most recent call last):   File "C:\Program Files\Python39\lib\urllib\request.py", line 1346, in do_open     h.request(req.get_method(), req.selector, req.data, headers,   File "C:\Program Files\Python39\lib\http\client.py", line 1279, in request     self._send_request(method, url, body, headers, encode_chunked)   File "C:\Program Files\Python39\lib\http\client.py", line 1325, in _send_request     self.endheaders(body, encode_chunked=encode_chunked)   File "C:\Program Files\Python39\lib\http\client.py", line 1274, in endheaders     self._send_output(message_body, encode_chunked=encode_chunked)   File "C:\Program Files\Python39\lib\http\client.py", line 1034, in _send_output     self.send(msg)   File "C:\Program Files\Python39\lib\http\client.py", line 974, in send     self.connect()   File "C:\Program Files\P

Change EMC Storage Management IP Address without Storage Reboot

Issue :  - How to Change EMC Storage Management IP Address without Reboot - Customer needs to change the IP address, subnet mask , default gateway of a CLARiiON or VNX for Block storage processor (SP)without rebooting the Storage Processors (SP) Scenario : EMC CLARiiON or VNX BLOCK Storage System Solution : 1) Download and Install Naviseccli utility  2)Run following command Add Security Parameters For SPA naviseccli -User admin -Password password -Address 172.XX.XX.XX -Scope 0 -AddUserSecurity For SPB naviseccli -User admin -Password password -Address 172.XX.XX.XX -Scope 0 -AddUserSecurity Get the info about existing SPs For SPA naviseccli -h 172.XX.XX.XX networkadmin -get For SPB naviseccli -h 172.XX.XX.XX networkadmin -get Change the IP Address For SPA naviseccli -h 172.XX.XX.XX networkadmin -set -address 172.XX.XX.XX -subnetmask 255.255.255.0 -gateway 172.XX.XX.XX naviseccli -h 172.XX.XX.XX networkadmin -set -address 172.XX.XX.XX -subnetmask 255.255.255

Fixed | WSUS 2016 | Error Code 0x8024401c | Windows 10 | Windows Server 2016

Scenario : Server : Windows WSUS Server 2016 Client : Windows 10, Windows Server 2016 Error Code :  0x8024401c on Windows 10 or Windows Server 2016 Solution : 1) Go to IIS Manager on WSUS Server 2) Goto Advance Settings of  WsusPool. 3) Make sure following settings are present/configured on the Pool, if not change it to below: Queue Length: 25000 Limit Interval (minutes): 15 "Service Unavailable" Response: TcpLevel Private Memory Limit (KB): 0 4) Make sure, the WSUS Entry in the Registry is having fully qualified domain name of WSUS Server. 5) Stop the IIS 6) Edit the web.config located at following location on WSUS Server : C:\Program Files\Update Services\WebServices\ClientWebService\web.config Replace <httpRuntime maxRequestLength="4096" /> with <httpRuntime maxRequestLength="204800" executionTimeout="7200"/> 7) Start the IIS 8) Retry updating clients. Done! Let me know if it has helped to y