Logo

Computer is stuck on the Hi there screen

As you know, installing Windows 10 is quite a complicated process in the background even though it may look like an easy task in the foreground. There are times when the setup is stuck on the “Hi there” screen where you won’t be able to input any information in the fields given and you wouldn’t be able to do anything else since the screen does not move ahead.

There are a lot of possible reasons why this issue occurs. It could be due to a damaged setup image, invalid boot configuration, and many more. To resolve this problem, there are several options you can check out. You can try to get a new setup image or run the Automatic Repair or you could also try to recreate the Boot Configuration files or BCD. To get started in checking out these solutions, make sure to follow the instructions provided below.

Option 1 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.

  • You can start by creating and booting from a bootable Windows 10 USB Stick.
  • After that, click on Repair your computer located on the bottom left corner when you are on the initial Windows Startup screen.
  • Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
  • Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

Option 2 – Try to rebuild the BCD files

You can also try rebuilding the BCD files to resolve stuck screen issue in your Windows 10 computer.

  • You can start by booting into the installation environment for Windows 10 from an installation media.
  • After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
  • From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
    • bootrec /FixMbr
    • bootrec /FixBoot
    • bootrec /ScanOS
    • bootrec /RebuildBcd
  • Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed error code 0xc000014c.

Option 3 – Try recreating the Windows 10 installation USB

Recreating the Windows 10 installation USB might help in fixing the problem. You can use a USB drive to do so but make sure that it has a great read-write speed. Follow the steps below to recreate Windows 10 installation USB”

  • Click this link and then click the Download Tool Now button.
  • Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
  • Now select the ISO file option in step 5.
  • After that, you should now have an ISO file.
  • Next, go to the location where you’ve downloaded the ISO file.
  • Then right-click on the Windows 10 ISO file and select the Open with option and then select File Explorer.
  • Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option 4 – Try getting a new Windows image file

If none of the four given options above worked, you might want to get a newer installation image using the Windows Media Creation tool. After that, create the bootable USB drive and once completed and then try to run the Windows 10 setup again.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

How to Fix Runtime Error 713
Runtime Error 713 is an error that occurs during the distribution of a Visual Basic application that includes a data report. The error is displayed on the screen when you try to open the data report from your desired application.

Error Causes

The reason why computer users often experience the Runtime Error 713 is that the data report run-time file also referred to as Msdbrptr.dll is not included in your setup package. Though this error does not pose any big threat to your computer, however, it is recommended to fix the error because the Runtime error 713 may hamper your ability to install and access new programs.

Further Information and Manual Repair

Don’t you panic if you see Runtime Error 713 message pop up on your PC? This error is rated easy to repair and can be fixed in a couple of minutes. There are two ways to fix Runtime Error 713. You can choose whichever 2 alternatives suit you best.
  • Method 1
First, open your project and include a reference to the data report file, the Msdbrptr.dll file. Locating this file is not difficult. It is listed as Microsoft Data Report Designer v6.0 in the reference dialog box. Sometimes you may see this file listed more than once. Now when this happens be sure to select the file that is associated with Msdbrptr.dll. After you select it, the reference will be verified. Once verification is complete, you are good to go. Now you can try rebuilding your setup package again.
  • Method 2
The second alternative is to add the Msdbrptr.dll file manually in PDW (the Package and Deployment Wizard). Simply add the file in the Included Files dialog box window and run the PDW. Now you are all set to rebuild your setup package. Whether you follow method 1 or 2 after you rebuild the setup package and the installation is complete, you will see the following files in the indicated folders:
  • <windows system>Msdbrptr.dll
  • <program files>Common Files\Designers\Msderun.dll
  • <windows system>Msstdfmt.dll
The presence of these files indicates successful installation and now you can easily try opening the data report. If you’ve noticed, all you have to do to fix Runtime Error 713 was to include the Msdbrptr.dll file. So, next time if you or your friends experience Runtime Error 713, you know exactly what to do and how to fix it.
Read More
Fix Windows was unable to repair the drive
If you connected your Hard Disk, USB, or SD card to your Windows 10 computer and you suddenly encounter an error that says, “Windows was unable to repair the drive”, read on as this post will help you fix the problem. This kind of error indicates that the file system on the drive has become corrupted and that ChkDsk was not able to repair the problem. You can also encounter this error when you try to run the ChkDsk utility to repair the system. This kind of error is most likely due to the general corruption of the contents in the drive. It is also possible that you removed the external drive without using the “Safely remove hardware” option or it could be that the drive is still in use. To fix the problem, the obvious thing to do is to safely remove the external drive by using the “Safely remove hardware” option. If it didn’t work, you can try to run the CHKDSK utility from the command line or you could also restart your computer in a Clean Boot State and then run the scan. Before you proceed with the potential fixes provided below, make sure that you create a system restore point first or you could also create a backup copy of the data to an external drive.

Option 1 – Run the CHKDSK utility from the command line

Although some users reported getting the “Windows was unable to repair the drive” when they run a CHKDSK scan, other users reported that running it also fixed the error. Thus, you can try to run it and see if it works or not.
  • In the Windows Search box, type “command prompt” and from the search results, right-click on Command Prompt and select “Run as administrator”.
  • After opening Command Prompt, type this command and tap Enter: chkdsk <Partition Letter>: /f
  • The command you entered will start to check for errors and fix them automatically. Else, it will throw an error message saying, “Chkdsk cannot run because the volume is in use by another process. Would you like the schedule this volume to be checked the next time the system restarts? (Y/N)”.
  • Tap the Y key to schedule Disk Check the next time your computer restarts.

Option 2 – Restart your computer in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that triggers the “Windows was unable to repair the drive” error to appear when you connect your external drive or run the CHKDSK utility. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.
  • Log onto your PC as an administrator.
  • Type in MSConfig in the Start Search to open the System Configuration utility.
  • From there, go to the General tab and click “Selective startup”.
  • Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
  • Next, click the Services tab and select the “Hide All Microsoft Services” check box.
  • Click Disable all.
  • Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
  • Once your computer has restarted in a Clean Boot State, perform your scan again and see if it now works, and then start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.
Read More
Switch audio devices in Windows 11 taskbar
windows 11 audio settingsWindows 11 has brought some new features and changed some of the existing ones. One of these changes includes quick switching of audio devices which will play audio. Audio switching can still be done under the taskbar, it is just a little different and one could say even hidden. Follow this quick guide and you will be switching from your headphones to speakers as an example in a matter of seconds.
  1. Click on the speaker icon located in the far-right part of the taskbar.
  2. After the quick settings menu appears click on the right arrow located right of the volume slider. If the arrow is not present, instead of click on the pencil icon, then on add, and finally select Volume from the list.
  3. After clicking on the arrow icon, a list of all enabled audio devices on the system will replace the volume slider. Click on the desired audio device in order to make it active.
  4. Click anywhere outside the quick setting menu to save changes and close it.
Note: in the Quick settings menu if you choose More Volume Settings it will bring you to System > Sound where you can access more sound input and output options.
Read More
How to Fix Windows Update Error 0x800706be
Error 0x800706be is a Windows error code that pops up when a particular system file is having some issue. This error pops up on other Windows-compatible software as well as driver vendors. This error signifies a misconfigured or corrupted system file so you might encounter this error in different instances. For instance, this error might pop up when you click the audio icon from the system tray or when the Windows Upgrade or Update has failed. Needless to say, this error can be caused by different factors. Anyhow, this post will show you what you can do to fix the problem when the error pops up during a Windows Update or Upgrade. If you are seeing this error when you try to install the latest Windows updates, it will show a Windows Update failed message and you obviously won’t be able to update your Windows 10 PC until you fix this error. You will keep seeing this error even when you try to reboot or update it a couple of times. As mentioned, the error code 0x800706be appears when there is something wrong with your system files – they are either corrupted or misconfigured. This error is most likely caused by the corrupted Windows Update Components. Corruption of these files is not unusual and it could happen anytime. So since the Windows Update files or components are corrupted, you won’t be able to successfully install the latest Windows Updates. Here are some options you can try to fix the problem.

Option 1 – Try running the Windows Update Troubleshooter

Running the Windows Update troubleshooter is one of the basic things to do when facing any kind of issue with Windows Updates. As long as it can it will detect the issue and automatically solve them so that there will be no need for you to do more technical steps to resolve the issue.
  • Tap the Windows and R keys on your keyboard to open the Run dialog box.
  • Then type in “control.exe /name Microsoft.Troubleshooting” in the field and tap Enter to open the Windows Update Troubleshooter.
  • After that, click Windows Update and follow the next on-screen instructions.

Option 2 – Try resetting the Windows Update Components

This is another basic thing to do in fixing the error 0x800706be. It is also one of the solutions that mostly worked for users who also got this error when trying to install Windows updates. And since the problem is caused by corrupted Windows update components, the most logical thing to do is to delete old files and reset components. To reset the Windows Update components, follow the given instructions below carefully.
  • Tap the Windows key once.
  • Then in the Windows Start Search, type in “command prompt”.
  • From the search results displayed, right-click on Command Prompt and select the “Run as administrator” option.
  • After that, type in “net stop wuauserv” and tap Enter.
  • Next, type in “net stop cryptSvc” and tap Enter.
  • Then type in “net stop bits” and tap Enter.
  • Type in “ren C:\Windows\Software\Distribution Software\Distribution.old” and then tap Enter.
  • Afterward, type in “C:\Windows\System32\catroot2\Catroot2.old” and tap Enter.
  • Next, type “net start cryptSvc” and tap Enter.
  • Then type “net start bits” and tap Enter.
  • Finally, type in “net start msiserver” and tap Enter.
  • Now close Command Prompt and then try updating Windows once more.
Read More
Choose what application will load on startup
Hello everyone and welcome to another great tutorial from errortools.com I hope everyone is feeling great and that you are prepared to boost the performance of your computer. This time we will speed up Windows startup time and overall performance by eliminating startup programs that we don't need and do not use. Microsoft itself and some application developers tend to have some applications or some services always active and set to be loaded on Windows startup. If you want to change which of these applications are starting up with your Windows and change them, follow this easy guide and you will be speeding up your Windows in no time. First thing is to open a task manager, fastest and most direct way of doing this is with a keyboard combination of CTRL + SHIFT + ESC keyboard with ctrl shift and esc markedWhen Task Manager opens, click on the startup tab on top. task manager startup tabOnce you click on startup you will get a list of applications that are set to be started when Windows is booted. startup applicationsYou can now click on the application and then click on disable on the bottom button, the application status will update in task manager to disabled and it will not be booted anymore when Windows starts. In this same manner, you can enable back some applications if you changed your mind about them. Please note that some applications are using some services and must have them running or they will not work properly. The best practice is to disable applications you are positive you will not use or use rarely so you do not want them to slow down Windows.
Read More
Step-by-Step Guide to Patching Error Code 24

Code 24 - What is it?

You may experience error code 24 when you try to use a device on your PC that is not properly installed or its driver is corrupted. Code 24 is a Device Manager error and it pops up on your computer screen in the following format:

“This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)”

Solution

driverfix boxError Causes

Error code 24 may be triggered due to several reasons. However, the most common causes for this error code include:

  • Incorrect device installation
  • Hardware failure/ conflict
  • Corrupted or outdated driver
  • Device prepared for removal

It is recommended to resolve the error code to ensure your PC works at its optimal performance. Error code 24 can lower the device functionality and PC performance dramatically.

Further Information and Manual Repair

Since this error code can mean several different things, troubleshooting it can be quite tricky but to make it simple to resolve, we have listed down some easy methods to repair error code 24.

Try these methods to fix error 24 on your PC and ensure your system works at its optimal pace. Let’s get started….

Method 1 - Update the BIOS on Your Motherboard

Problems with BIOS, the controlling software in the PC motherboard, can sometimes trigger hardware conflicts resulting in Device Manager error code pop-ups.

In such a scenario, it is advisable to update BIOS. To update, go to your PC motherboard manufacturer’s website. Here you will be able to find instructions on updating BIOS.

Follow the instructions carefully to resolve error code 24 on your system. If the error code still persists, then try other methods discussed below.

Method 2 - Remove New Devices

If you experienced code 24 on your PC after installing new devices, then it is advisable to remove them to resolve the error code.

If the device is attached to your computer, then simply disconnect and remove it immediately. Once you disconnect it, reboot your system to activate changes.

Method 3 - Update Drivers

If device removal does not resolve the problem, then consider updating the device driver. Code 24 is also related to driver problems.

It can occur if a device driver is corrupted or outdated. In such an event, it is advisable to update the driver by installing the new and latest device driver version on your PC.

For doing this, simply download the latest device driver version from the manufacturer’s website and update it.

Method 4 - Install DriverFIX for Both Device Driver Update and Safe Device Removal

Finding problematic drivers and the latest device driver versions to update them, however, can be time-consuming and sometimes even frustrating. To avoid being in this situation, it is advisable to download DriverFIX.

DriverFIX is a cutting-edge, user-friendly and an innovative program exclusively designed to resolve device driver related issues and problems on computer systems

It is integrated with the newest technology and intelligent programming system that enables and empowers PC users like you to repair device driver error codes in seconds.

Once you install this software on your PC, simply run it. The software program instantly detects all problematic drivers and updates them with their latest versions available on the internet.

All this is done in mere seconds and it’s not time-consuming at all. Moreover, device driver updates are performed frequently to ensure that you don’t experience any driver problems again.

  • With this software on your PC, you don’t have to worry about updating drivers regularly.
  • In addition to this, as we discussed above, driver code 24 can also occur due to new plugged-in devices. If that’s the reason, then DriverFIX can help you resolve this problem too.
  • It can help you manage and unplug USB devices safely from your PC. After installing DriverFIX, unplugging USB devices is easy and you don’t have to worry about data corruption or drive damage.
  • DriverFIX manages USB devices smoothly by making the ejecting process easy and safely removes hardware from your PC, thereby resolving error code 24 in no time.
  • DriverFIX is easy to install and use and is compatible with all Windows versions.

Click here to download DriverFIX and repair Device Manager error code 24 right away.

Read More
Setting a default printer in Windows 10
Windows 10 is by far the most personalized Windows so far, most of its personalization comes from him learning our habits on computers and setting future experiences taking them into account. One of these things that Windows likes to set for us is also the default printer. The default printer is set as one which is most used but sometimes we do not want that, we might like to use another printer as default despite Windows choosing one for us. Never worry, setting default printer is easy and this guide will take you to step by step journey of how you can do it in 5 min on your personal computer. Let us begin: First thing is to click on the windows icon on the bottom left and open start menu, from start menu click once on settings. Windows 10 Star menu with marked settings iconWhen the settings window opens, choose DEVICES on it. Windows settings with marked devices sectionOnce the device window opens, click once on printers and scanners, and on the right window go to the bottom and uncheck Let windows manage my default printer. Windows settings for printerUnchecking that box will let Windows know that we do not wish anymore for him to set our default printers according to their use. Once the checkbox is clear go up to your printer list and click on the printer you wish to use as the default one. I will choose Microsoft Print to PDF as my default printer and click on it. Once the printer is clicked option menu will appear. Windows settings manage printerWhen the option menu appears under the printer name, click on Manage which will take you to the printer management screen. When you are on the manage screen, click on the Set as default button, and you are done. Windows settings printer setting
Read More
Fix Cannot load Management Console
TPM, also known as Trusted Platform Module, is a specialized chip used for security as well as encryption of users’ private data like Fingerprint, Facial data, and many more. TPM also comes with a Management Console and if you are not able to load the Management Console and you got the “Cannot load Management Console” error instead, read on as this post will guide you in fixing the problem. This type of issue usually happens when you clear or disable the TPM using the settings in the BIOS and so when you run the Trusted Platform Module Management console, you encounter the error. To fix the “Cannot load Management Console” error in your Windows 10 computer, here are some options you should check out.

Option 1 – If TPM is cleared in the BIOS:

If the Trusted Platform Module is cleared in the settings of the BIOS, you have to close and restart the TPM Management console or TPM.msc once again. It could be that the TPM Management has to reload the changes again after you’ve made them which is why you encounter the “Cannot load management console” error.

Option 2 – If TPM is disabled in the BIOS:

If you opted to disable TPM using the BIOS settings or you have turned it off by accident, then you have to enable it back and you have two options to do that – you can either enable TPM from the BIOS or using the Windows PowerShell. For more details, refer to the instructions below.

Enabling TPM from the BIOS:

  • You need to first reboot your PC and then go to the BIOS.
  • From there, look for TPM under the security options and in case the TPM management option has been disabled or greyed out, refer to the sub-steps given below to make it active again
    • Enable the Admin password in the BIOS.
    • Then go back to the TPM settings and check if the TPM management is already available.
  • After that, you should now be able to enable TPM. Remember that it’s always a good idea to have an ADMIN password for your BIOS as it makes sure that no one can change the settings in your computer BIOS and Security level options.

Enable TPM via Windows PowerShell:

  • This second option is a lot easier compared to the first one if you have admin privileges. So once you’ve opened the Windows PowerShell with admin privileges, you need to run the following command:
    • $tpm = gwmi -n rootcimv2securitymicrosofttpm win32_tpm
    • $tpm.SetPhysicalPresenceRequest(6)
  • After you execute the commands given above, you need to restart your computer.
  • Now, once your computer has restarted, you need to accept any BIOS prompts and then check if the “Cannot load management console” error is now fixed.
Read More
The server did not register with DCOM
There are times when after you upgrade your Windows operating system, the System Logs under the Event Viewer will display an error message saying, “Event ID 10010 error – The server did not register with DCOM within the required timeout”. What is DCOM? DCOM stands for “Distributed Component Object Model”. It is a proprietary Microsoft technology that allows the Component Object Model or COM software to communicate across a network. You can consider it as an extension of COM which is equipped with the capability of solving a couple of inherent problems related to the COM model to the better use over a network. COM is a tool that’s used for advanced configuration and troubleshooting in Windows 10. Developers usually use it to configure routine components and application behavior like participation in transactions and object pooling and so on. The Component Services needs the DCOM wire protocol in order to communicate with the Component Object Model components on other computers. By default, in a Windows-based system, the network computers are configured initially to enable DCOM. There are also some components in Windows that might require registering themselves with DCOM. However, if they fail to do so, you will encounter the “The server did not register with DCOM within the required timeout” error. To fix this, here are some suggestions you can check out.

Option 1 – Try to use the Component Services

  • Tap the Win + R keys to open the Run dialog box.
  • Then type “dcomcnfg” in the field and tap Enter to pull up Component Services.
  • Next, double click on the Computers folder located in the right pane and right-click on My Computer, and select the Properties option.
  • After that, switch to the COM Security tab under My Computer Properties and then go to the Access Permissions section.
  • From there, click the Edit Default button and in the new window that appears, apply the correct permission to objects under the Group or user names section.
  • Once you’re done, click OK and exit. This should fix the error.

Option 2 – Make sure that Function Discovery Resource Publication Properties Services is running

  • In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
  • Next, scroll down and look for the “Function Discovery Resource Publication” entry and double click on it.
  • Then switch to the General tab and from there, make sure that the Startup Type is set to “Manual (Triggered).
  • You also have to make sure that the service is running so if it’s not, just click on the Start button to start the service.
  • Now click on Apply to save the changes made.

Option 3 – Try resetting the default DCOM permissions

  • Tap the Win + R keys to open the Run dialog box.
  • Then type “dcomcnfg” in the field and tap Enter to pull up Component Services.
  • After that, expand Component Services > Computers and right-click on My Computer, and then select Properties.
  • Next, go to the Default Properties tab, and in the Default Distributed COM Communication Properties section, make sure that:
    • Default Authentication Level is set to Connect
    • Default Impersonation Level is set to Identify.
Read More
Fixing the “Failed to register a VB Script dll” Error in Windows 10
If you open any program in your Windows 10 PC such as Outlook and suddenly get an error message saying, “Failed to register a VB Script dll. Reinstall or run Regsvr32.exe Vbscript.dll to self-register”, read on, as this post will guide you on what you can do to fix it. The obvious solution to this problem is by re-registering the “vbscript.dll” file on your computer. Refer to the instructions given below to re-register the VB Script DLL file and to fix the error.
  • Step 1: Open the Command Prompt as an administrator from the WinX Menu.
  • Step 2: After opening Command Prompt, type in the following command and tap Enter on your keyboard.
regsvr32.exe vbscript.dll
  • Step 3: Once you enter the command, it will re-register the VB Script DLL file using the Windows OS tool called Regsvr32 or regsvr32.exe. This tool is a command-line utility used to register and unregister OLE controls such as DLL and ActiveX (OCX) controls in the Windows environment. After the execution of the command, you should see the following pop-up on your screen which means the re-registering of the concerned DLL file has succeeded.
On the other hand, if re-registering the DLL file didn’t work, then you can try logging in using an administrator account and then register the DLL file again or you could also use the System File Checker to figure out what the problem really is and automatically fix it. System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.
  • Tap Win + R to launch Run.
  • Type in cmd in the field and tap Enter.
  • After opening Command Prompt, type in sfc /scannow
The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:
  1. Windows Resource Protection did not find any integrity violations.
  2. Windows Resource Protection found corrupt files and successfully repaired them.
  3. Windows Resource Protection found corrupt files but was unable to fix some of them.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status