One of the most useful utilities for advanced users in Windows is the Windows command line or Command Prompt. It is efficient in fixing system files, checking the disk for errors as well as other intensive tasks that are made convenient using this.
One of the tasks you can carry out using Command Prompt is repairing the Windows bootup process if it encounters any issues. However, if you tried running the “bootrec/fixboot” command and you receive an error message saying, “Element not found”, read on as this post will guide you in fixing this error. This kind of error in the command line could be due to a damaged BCD or MBE, inactive system partition, or it could also be that there is no drive letter being assigned to the EFI partition. Whichever the case is, here are some possible fixes that should help you resolve the problem.
As mentioned the error could be caused by a damaged BCD and so to fix the problem, you need to repair BCD by following these steps:
bootrec /fixboot
ren BCD BCD.bak
bcdboot c:Windows /l en-us /s b: /f ALL
diskpart
list volume
select volume number
assign letter=<LETTER>
Note: Make sure to replace “<LETTER>” with the letter you want to allocate to that partition. Afterward, it will assign a letter to the selected volume.
Like the first given option, you also have to make sure that you have a bootable Windows 10 USB drive before you proceed to set the System Partition to Active. Once you have it covered, refer to these steps:
diskpart
list disk
select disk number
list partition
select partition number
active

“In Microsoft Windows accounts protected by Family Safety settings, secure connections on popular websites like Google, Facebook and YouTube might be intercepted and their certificates replaced by a certificate issued by Microsoft in order to filter and record search activity.”And if you are connected to a corporate network, there might be a monitoring/filtering product that could be replacing certificates. Moreover, there are also users who reported getting this issue when they use the Nightly version of Firefox. And if that’s the case, you have to try accessing secure websites using only the stable build especially when it comes to payments. However, if you are not doing that, then here are some options you need to check out.
“The application failed to initialize properly (0xc0000005). Click on OK to close the application.”This kind of application error can occur due to several reasons which include damaged installation of the application or system files may have gotten corrupted or damaged. It could also be caused by a malware infection. There are a couple of suggestions provided in this post to help you resolve the error. You can try to run both a System File Checker scan and the DISM tool or reinstall the problematic application or repair-install Windows 10 as well as run a malware scan. Note that the options provided below do not have to be followed in sequence.
chkdsk /f /r
Users, when upgrading to Windows 10 from Windows 7 or Windows 8/8.1, or when upgrading to a new version, build, service pack, or major update of Windows 10, can encounter error code 0xC1900101, 0x30018. Windows 10 installation fails and stops or hangs. During the installation process, it will reach a certain maximum limit (normally at 6% or 32%) then reverts back to the previous version of the operating system and displays the following message:
We couldn’t install Windows 10. We’ve set your PC back to the way it was right before you started installing Windows 10.
0xC1900101 – 0x30018 The installation failed in the FIRST_BOOT phase with the error during the SYSPREP operation.
Error CausesIn attempting to fix Error Code 0xC1900101-0x30018, it is vital to know what causes this issue. The most probable causes of this error are:
NOTE: If this fails, if possible, you can try using the .ISO file in upgrading.
If you’re using Windows Update in installing Windows 10, you can implement the following:
NOTE: Don’t forget to hit Enter after every command.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
NOTE: Don’t forget to hit Enter after every command.
ren
C:WindowsSoftwareDistribution SoftwareDistribution.old
ren
C:WindowsSystem32catroot2 Catroot2.old
NOTE: Don’t forget to hit Enter after every command.
net start wuauserv
net start cryptSvc
net start bits
net start msiserver