Skip to main content

How to fix boot error 0xc000000f in Windows Server 2008?

By



If you face with error like above picture, take note it's your BCD corrupted.
You can fix that error as below.

Boot your server with Windows CD/DVD and go to commmand prompt when you reach repair option.

Type following command when you reach in Command Prompt Windows.

>rename C:\Boot\BCD bcd.old
>Boortrec /rebuildbcd
>dispart
>select disk 0
>select partition 1
>active
>exit

Restart the Server and Boot up with Hard Disk.

You can see that your Server Windows is as in good working condition.

Why this error come out??? It might be if meet with one/two or all of the following condition,

- Virus infected system files
- You had to use force shutdown the server that installed Hard Disk controller such as SCSI or RAID or etc.
- You had to attach or deattach the NAS or USB Drive that connect with Server and that make change BIOS configuration. But you didn't notice to re-configure changed configuration and boot up server. Then server will not able to boot up.

May you all be happy.
(Be knowledgeable, pass it on then)

Labels:

Comments

  1. DTM_NVFebruary 13, 2013 at 6:01 PM

    I think you mean:
    >bootrec /rebuildbcd
    >diskpart
    >select disk 0
    >select partition 1
    >active
    >exit

    ReplyDelete
  2. JamesMay 15, 2013 at 11:17 AM

    Thank you, thank you, thank you.

    ReplyDelete
  3. AnanadJuly 2, 2020 at 4:56 AM

    This comment has been removed by the author.

    ReplyDelete

Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

By
I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...
Post a Comment
Read more

Why do we need network virtualization?

By
We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...
145 comments
Read more

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

By
Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API.  Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace:    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Soc...
7 comments
Read more