• What kind of error an error occurred while. What to do if Roblox displays the error “an error occurred while starting” and does not start. What does error occurred while attempting to read mean?

    Good afternoon, dear readers, today I want to tell you how to solve the error an error occurred while attempting when loading Windows. This instruction is suitable for both client operating systems such as Windows 7, 8.1 and 10, and for Windows Server. Fixing this problem will take you no more than 10 minutes, even in the case of a server, this is not such a big downtime.

    What does error occurred while attempting to read mean?

    And so I’ll tell you what happened to me. We have a blade basket with hs22 blades, they don’t have their own disks and they are loaded via fc from netApp storage, after an accident on one of the blades when Windows Server 2008 r2 was loading, this error popped up

    File:\EFI\Microsoft\Boot\BCD

    status: 0xc000000f

    The error shows that the operating system cannot boot due to the bootloader in the EFI\Microsoft\Boot\BCD file.

    Causes of error 0xc000000f

    • Windows boot loader is damaged
    • Accidentally deleted the boot area

    Bootable hard drive partition table with UEFI GPT

    You must have at least three sections.

    • EFI system partition (ESP – EFI System Partition) – 100 MB (partition type - EFI)
    • Microsoft backup partition – 128 MB (partition type - MSR)
    • Primary Windows partition – Windows partition

    Or is there an additional section?

    • Windows RE

    Let's talk now about each of them in more detail.

    Windows RE

    Windows RE is a 300 MB partition on a GPT partition, and its purpose is to contain bootloader recovery data. The same one is also available in systems with MBR markup, 350 MB in size; it is also called System Reserved and, along with RE, contains the files necessary to boot Windows.

    The recovery environment is in the file winre.wim

    Windows RE is created during the Windows installation process.

    1. During the process of creating a partition structure for Windows RE, a special attribute 0x8000000000000001 is assigned. It is a combination of two attributes - one blocks automatic drive letter assignment, and the other marks the partition as required for system operation, which prevents it from being removed from Disk Management.
    2. The system image is applied to the Windows partition - standard install.wim or customized custom.wim. As a result, winre.wim ends up in the Windows\System32\Recovery folder.
    3. The Recovery\WindowsRE folder is created on the Windows RE partition, after which this recovery environment location is registered by the utility reagentc.

    W:\Windows\System32\reagentc.exe /setreimage /path T:\Recovery\WindowsRE /target W:\Windows

    reagentc.exe is included in Windows and is launched from the operating system partition. Along with registering the RE, the command moves winre.wim from the Windows partition to the Windows RE service partition. If you want to see the file, first assign a drive letter using the diskpart utility. Since the file has system and hidden attributes, the fastest way to show it is dir /ah.

    As a result of these steps, the recovery environment is booted from the Windows RE partition. I will show the details of the process in an upcoming story about restoring a backup.

    The Windows RE partition is not required for Windows to function. The recovery environment may be absent or located directly on the partition with the operating system. However, placing Windows RE on a separate partition serves two purposes:

    1. Booting into the recovery environment on a PC with an encrypted Windows partition. It is impossible to boot into the recovery environment if it is on a Windows partition that is encrypted. The Windows RE partition is excluded from encryption, so you can always get into the environment and use its tools.
    2. Protecting your recovery environment from rogue hands. Since the partition cannot be deleted in Disk Management, it is somewhat less likely to die due to carelessness, although it is not difficult to delete it using diskpart if you wish.

    System (EFI) partition

    Chapter EFI, formatted in FAT32, is required for GPT partitioning on UEFI systems. The standard EFI partition size is 100MB, but on 4K Native Enhanced Format drives (4KB sectors) it is increased to 260MB due to FAT32 limitations. PC manufacturers may store some of their tools on this section, so its size varies depending on the manufacturer.

    In GPT partitioning, the EFI partition performs one of the roles assigned to the System Reserved partition in MBR partitioning. It contains the boot configuration store (BCD) and the files needed to boot the operating system.

    MSR (Microsoft System Reserved) partition

    This section is also required for GPT markup. It is formatted in NTFS and takes up 128MB in Windows 8 and 8.1, and 16MB in Windows 10. GPT does not allow the use of hidden sectors of the disk (unlike MBR), so the MSR partition is required for utility operations of built-in and third-party software (for example, converting a simple disk to a dynamic one).

    Despite the presence of “System Reserved” in the name, the MSR partition has nothing in common with the System Reserved partition in the MBR partition. Additionally, it is not visible in file managers and Disk Management, although diskpart shows him.

    Windows partition

    This is the operating system partition to which the standard install.wim image or a customized image is applied.

    Eliminate error occurred while attempting to read

    As you remember, we caught this thing

    An error occurred while attempting to read the boot configuration data

    File:\EFI\Microsoft\Boot\BCD

    status: 0xc000000f

    Now let's understand both graphical methods and command line methods.

    Recovery utility only for Windows client

    Here we will use Windows restore points, they are included by default in client Windows 7, 8.1, 10, and this is logical in order to quickly recover from some system glitches. Here we need a bootable flash drive with the same version of Windows; if you have, for example, WIndows 8.1 64x, then the flash drive should have a 64-bit version.

    For Windows 7, it looks like this

    Once you start loading the Windows 7 distribution from a bootable USB flash drive, you will see an installation window; in the lower corner, click System Restore.

    You will have options, the very first option is to select Startup Repair

    An attempt will be made to restore Windows 7 boot areas

    Click Fix and reboot.

    If after rebooting you still have an error, then go back to this menu and select the second item, System Restore Windows 7. The utility will find the installed operating system and try to roll back it to the moment when it worked correctly, your personal data will not be affected, at most you You may run out of programs.

    For Windows 8.1 and 10, it looks like this

    The error an error occurred while attempting to boot can be solved in the same way; you create a bootable USB flash drive with Windows 8.1, as you can do in the link above. Boot from it and you will find yourself in the recovery environment. Also on the installation window, click system restore.

    Troubleshooting > Option 1 Restore the computer to its original state, saving files and option 2 Advanced options > System Restore or System Image Restore.

    After a reboot, everything should be fine for you, this is an advantage of desktop platforms, from server Windows Servers, since in server versions everything is disabled by default and the administrator needs to enable everything himself, but disabled to save resources, but from my point of view They could make an exception for recovery points.

    Recovery for everyone via command line

    This method is more complex, especially for those who see the command line of the operating system for the first time. This method is suitable for both 7,8.1,10 and Windows Server 2008 R2 and 2012 R2. In this method, you will also need a bootable USB flash drive with the required distribution of your OS. I will show the example of Windows Server 2008 r2, but all the steps, as I wrote, are suitable for any OS, starting with W7.

    The only other digression is that if, like me, your operating system crashed on the blade server, then do the first step; if you have a regular PC, then just skip it.

    1 Part only for blade servers

    • Since I have a blade system, in order to load the distribution kit there for repair, I will need to edit the ISO image, this is easy. Go to Blade Center, select Remote control and select the desired blade via java KVM. At the top, click Remote Drive > Select Image

    We indicate the path to our ISO

    Select the desired blade to mount from above and check the Write Protect checkbox, then Mount All.

    We see that the ISO is mounted, close this window.

    Now in the Boot menu, select boot from DVD Rom. As a result, the download will begin from your ISO inserted into the Virtual CD-rom.

    Part 2 for everyone

    You will see a standard loading bar.

    You will see a language selection window

    If your distribution is English, then to open the command line press Shift+F10, if Russian, then select the US international keyboard layout, since further commands will be entered on this layout, click next

    Select the layout in the next window, click the usual recovery menu.

    In the server OS, as I told you, you will not see checkpoints. Select the second item and further.

    And here it is the long-awaited command line

    In Windows 8.1, 10 and Server 2012 R2, you can get to the command line in the same way, but the menu has been slightly modified. You also go into recovery, then diagnostics.

    And here we will now look at several methods.

    1 method to eliminate an error occurred while attempting

    In the first method, we will execute two commands that restore the boot area. We use the Bootrec command. Enter it on the command line, you will see a list of attributes.

    • /FixMbr > will restore the MBR record, it won’t work with UEFI
    • /FixBoot > makes a new entry to the system partition
    • /ScanOs > search all Windows disks
    • >rebuildBcd > scan all OSes and add them to the boot menu

    Run Bootrec.exe /FixMbr, then Bootrec.exe /FixBoot

    Both commands worked normally, a new boot record was written to the first sector of the boot partition, and the second command wrote a new boot sector. We write Exit and reboot.

    Method 2 to eliminate an error occurred while attempting

    If the first method did not help you, do not rush to get upset, just load into the command line and enter the following commands.

    Bootrec/ScanOs, it will scan all your hard drives and partitions for the presence of operating systems and if any are found, an appropriate warning will be issued. Then you need to enter the command Bootrec.exe /RebuildBcd, this utility will offer to add the found Windows to the boot menu, we agree and enter Y and press Enter, all the found Windows are added to the boot menu

    in addition, you can immediately write bootsect /NT60 SYS, but if you have UEFI, you will get an error.

    If everything is ok, you will receive an updated bootcode area,

    Reboot and enjoy life. Below are the methods for UEFI.

    Method 3 to eliminate an error occurred while attempting for UEFI

    We also boot into command line mode and enter

    list disk >

    Let's select the disk on which Windows 8 is installed (if there is only one hard disk in the system, its index will be zero):

    Let's display a list of partitions in the system:

    In our example, we can see that the EFI partition (which can be identified by its size of 100 MB and the FAT32 file system) has an index of volume 1, and the boot partition with Windows 8.1 installed has a volume of 3.

    Let's assign an arbitrary drive letter to the hidden EFI partition:

    select volume 1
    assign letter M:
    Finishing work with diskpart:
    exit
    Let's go to the directory with the bootloader on the hidden partition
    cd /d m:\efi\microsoft\boot\
    Let's recreate the boot sector: on the boot partition
    bootrec/fixboot
    Let's delete the current BCD configuration file by renaming it (saving the old configuration as a backup):
    ren BCD BCD.bak
    Using the utility bcdboot.exe let's recreate the BCD storage by copying the boot environment files from the system directory:
    bcdboot C:\Windows /l en-us /s M: /f ALL

    Where, C:\Windows– path to the directory with Windows 8.1 installed.
    /f ALL– means that it is necessary to copy boot environment files, including files for computers with UEFI or BIOS (theoretical ability to boot on EFI and BIOS systems)
    /l en-us- system locale type. The default is en-us - English (United States).

    If you use the Russian version of Windows 8.1, the command will be different:
    bcdboot C:\Windows /L ru-ru /S M: /F ALL

    This is what the structure actually looks like

    Method 4 to eliminate an error occurred while attempting for UEFI

    We also boot into command line mode and enter

    list disk > look at the list of partitions in the system

    My operating system is on a 100 gig drive with the letter C.

    Using the list disk command we will see a list of disks

    I'm interested in Disk 0 because the system is on it. Let's choose him.

    List partition > Display a list of partitions

    Select partition 1 > Select the one with the bootloader (If there is a system one, then it is, if it is not there, then Registered) Delete both of them anyway

    Killing the first and second partitions (System and registered)

    Delete partition override

    Let's enter List partition again and make sure that both are deleted. Now we can manually recreate the EFI and MSR partitions. To do this, in the context of the diskpart utility, run the following commands:

    Let's copy the EFI environment files from the directory installed Windows 2008 R2, yours may be different:

    mkdir G:\EFI\Microsoft\Boot

    xcopy /s C:\Windows\Boot\EFI\*.* G:\EFI\Microsoft\Boot

    Let's go to the next step to solve the error: an error occurred while attempting

    Let's recreate the Windows Server 2008 R2 bootloader configuration:

    g:
    cd EFI\Microsoft\Boot
    bcdedit /createstore BCD
    bcdedit /store BCD /create (bootmgr) /d “Windows Boot Manager”
    bcdedit /store BCD /create /d “Windows Server 2008 r2” /application osloader

    The command returns the GUID of the created entry; in the next command, this GUID must be substituted instead of (your_guid)

    bcdedit /store BCD /set (bootmgr) default (your_guid)
    bcdedit /store BCD /set (bootmgr) path \EFI\Microsoft\Boot\bootmgfw.efi
    bcdedit /store BCD /set (bootmgr) displayorder (default)

    Further commands are executed in the context (default)

    bcdedit /store BCD /set (default) device partition=c:
    bcdedit /store BCD /set (default) osdevice partition=c:
    bcdedit /store BCD /set (default) path \Windows\System32\winload.efi
    bcdedit /store BCD /set (default) systemroot \Windows
    exit

    We all reboot and try to start your computer or server. More options.

    1. Turn off the power to the PC
    2. Disconnect (physically) the hard drive
    3. We turn on the PC, wait for the boot error window to appear, and turn it off again.
    4. Connecting the drive back

    Method 5 to eliminate an error occurred while attempting

    There is another method to solve the error an error occurred while attempting and 0xc000000f, and this is Acronis Disk Director software. There is such a boot disk Acronis Disk Director for repair, there is a laptop with two OSes, the first is Windows7, and the second is Windows 8.1, and both do not boot, we boot from our Acronis Disk Director

    I hope that the error an error occurred while attempting when loading Windows has now disappeared and you have booted. The error is that on both hard drives the first hidden System Reserved partitions should be marked with a red flag. On Windows 7, the volume of such a partition is 100 MB, and on Windows 8, 350 MB, these sections have the following attributes: System. It is active and it is on these partitions that the boot storage configuration files (BCD) and the system boot manager file (bootmgr file) are located. And it turns out that these attributes are carried by other sections. Because of this, Windows 7 and Windows 8.1 will not boot.

    Select the first hard drive 1, right-click on the first System Reserved partition and select “Mark as active”

    The volume Reserved by the system will be marked as active. Click OK.

    We do the same with Disk 2. Acronis Disk Director works in pending operation mode; for the changes to take effect, click the “Apply pending operations” button

    Continue. As you can see, after our changes, those sections that were needed became active.

    I hope you were able to resolve the errors an error occurred while attempting and 0xc000000f

    Download Roblox

    Sometimes apps and games can crash. One of the common errors in Roblox was “an error occurred while starting roblox.” Occurs when the user launched the game, but a system error occurred. It can be solved using several methods.

    How to fix the situation?

    First way, which helped many players - uninstall and reinstall the game. To get rid of all software components, the user must go to “Remove or change programs” and find Roblox in the list. After that, go through all the folders where the game may be located. Complete removal ensures that you can reinstall again correctly and without various problems.

    Second way: Disable antivirus. As in the first one, you will have to reinstall the game. Sometimes programs to protect your computer from various malicious files can react to the most harmless objects. If Roblox has been installed, it can be added to secure applications and opened using Administrator rights. In some cases, the problem is with the game update.

    Third method: Disable proxy server. This problem does not occur to everyone, but it can affect the ability to start. Solution using Windows as an example: go to the network settings in the bottom panel and go to the “Network and Sharing Center”. In the window that opens, find the “Internet Options” item and go to the “Connection” tab. In the “Network Settings” section, uncheck the “Use a proxy server” checkbox. If the mark was not set, then press twice and restart the device.

    Error downloading updates "An error occurred while updating" on Steam (for Dota 2, Counter Strike and other games) is not so rare. Its appearance is directly linked to official updates on Steam. The updates themselves are designed not only to make changes to the interface, but also to optimize a large number of internal processes. These innovations should help players in the gameplay, but not always everything goes smoothly.

    An error occurred while downloading updates

    Causes of errors when downloading updates

    The conflict itself, as a rule, arises due to the very client on the user's computer. Its installation may not be completed correctly, which subsequently prevents updates from integrating correctly. Unfortunately, if the files are interrupted halfway through unpacking the updates, then the situation cannot be easily corrected.

    Dota 2 And Counter Strike most frequently updated in the application Steam. It is with them that the error “An error occurred while updating” is most often associated. The problem appears when changes are made globally, where hundreds of meters of archives are subject to updating. Therefore, minor updates can be installed quite normally, without revealing conflict situations for a long time.

    What to do about this error?


    These solutions should be used first. If you've tried everything and nothing helps, then go to the official ones. developer recommendations.

    Resuming Steam from saves

    Steam is most susceptible to various types of errors. Therefore, Valve always invites its users to make backups all utility files. If you are one of those lucky people who have a backup copy, then feel free to try the next option.


    If an error occurred while updating games on your PC, then you should apply all the methods described above one by one. There is also a request to unsubscribe in the comments about the results.

    A post for the case when Roblox also gave you the error “an error occurred while starting” and does not want to start. This opportunity does not happen very often, but, as practice shows (and statistics of queries in search engines), sooner or later many users have to deal with it.

    On the other hand, the problem also cannot be called very complex and in the vast majority of cases it is eliminated using quite standard methods. We’ll tell you about them now. So,..

    what to do if Roblox shows the error “an error occurred while starting”

    So, in order, from simple to complex (in terms of the amount of work):

    #1 - reboot the router

    The technique is simple, but in this case, very effective. Since Roblox automatically connects to the Internet when it starts, any network failure at this moment can actually prevent the application from starting normally. Therefore, if we see an error launching Roblox, then go to and press the button on it Reset ". Or, if one is not found, simply unplug the device from the outlet, wait 1 minute , then turn it on, return to the game and try to log in again.

    #2 - disable the “Use a proxy server for local connections” function

    To do this:

    • on the keyboard press " Win+R ", in the line " Execute» we write inetcpl.cpl and click Enter ;
    • In the window that opens, uncheck the “ Use a proxy server for local connections«;
    • and click OK at the bottom of the window.
    #3 - temporarily disable the antivirus

    As we already said, the Roblox app requires an internet connection during the launch phase. due to some of his “convictions” he can prevent this. Thus, to resolve this conflict, the easiest way is to temporarily disable the antivirus. For most modern antivirus programs, you can get to the “switch” through the tray icon (lower right corner of the screen).

    In other words, we find the icon, right-click on it and in the menu that appears, click on the line with a name like “ Pause protection" or " Exit". If there is nothing similar in the menu, then double-click on the same tray icon to open the main antivirus settings window and find the desired button there.

    #4 - add Roblox to the Windows Defender whitelist

    The reason for the error " error occurred while starting"may also be standard . In this case, you can resolve the problem by adding the Roblox application to the list of allowed Defender programs. This is done like this:

    • if you are not logged into the system using an administrator account, you need to re-login;
    • go to " Settings "Windows, click " Update and Security ", Then - " Windows Security " (left) and the " button Open Defender Security Center "(right);
    • then click “ Firewall and Network Security " and in the next window - the link " Allow applications through the firewall «;
    • press the button " Change settings ", indicate Roblox and click " Add «;
    • after the application is added to Defender, set permissions for it and click OK .
    #5 - reinstall Roblox

    This measure, of course, is advisable if the previous four did not have the desired effect, and the application persistently does not want to start. Therefore further:

    • press from the keyboard Win+R, in the line " Execute» we write appwiz.cpl ;
    • find and highlight in the list of programs Roblox and then click the button “ Delete «;
    • we confirm the command, wait for the removal procedure to complete and reboot the computer;
    • after that we come in to the game page in the Microsoft Store and download Roblox again;
    • find the installation file, right-click on it and select “ Properties «;
    • in the window " Properties"open the tab" Compatibility ", activate the option " Run the program in compatibility mode ", select the OS version in the menu and press the button " Apply "at the bottom of the window.

    Read more: