0x8019019a when setting up Yahoo Mail

Booting the Windows computer system includes loading it from the various boot devices such as drivers, network as well as USB drives when the computer is turned on. The instant the startup sequence is done loading the operating system the system hardware will be ready to perform some complex operations – in this process, the Boot Log in Windows 10 is a record that maintains the list of success or failure of many pieces of Windows 10 system during the booting process. In other words, the Boot Log is the one that keeps a record of all that has happened while loading from the computer storage system to the memory during the boot process. It is available for several devices like network, hardware devices, and the operating system which assist in detecting issues during the boot process and other issues with regards to troubleshooting. Through Boot Log, you’ll know which drivers were unloaded and loaded from the start of the system during the boot process. You have the option to either disable or enable this feature on your Windows 10 PC. Named as “ntbtlog.txt”, the log file lists all the successfully loaded processes and the unsuccessful ones during the boot process. It is saved to the drive C:Windowsntbtlog.txt. As mentioned, you can enable or disable this feature in two ways – the first one is by using the System Configuration or MSConfig while the second one is using the Command Prompt. In this post, we’ll show you how you can enable or disable Boot Log in Windows 10 either way.

Option 1 – Enable or Disable Boot Log using System Configuration

Enable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and check the checkbox labeled “Boot Log” under the Boot options so that you can enable the Boot Log feature.
• Then click on OK to save the changes made.
• Next, click on the Restart button in the prompt window to get started with the Boot Log process.
• After restarting your PC, go to C:Windowsntbtlog.txt to open the boot log.

Note: As pointed out earlier, the log file contains a list of all the successfully loaded drivers and also the list of drivers that failed to load during the boot process and every time you restart the system, the boot log file will keep on updating and will eventually increase the list of entries. For you to locate the drivers and make your troubleshooting a lot easier, I advised disabling the boot log after troubleshooting. To disable the boot log using System Configuration, refer to the steps below. Disable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and unmark or uncheck the checkbox labeled “Boot Log” under the Boot options so that you can disable the Boot Log feature.
• Then click on OK to save the changes made.

Option 2 – Enable or Disable Boot Log using Command Prompt

Enable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• After opening Command Prompt, type in “bcdedit” and tap Enter.

Note: You have to find the Identifier of the current operating system first to enable the Boot log. You can find it under the Windows Boot Loader section in the “Description” field and in this case, it’s Windows 10. You can also find the operating system identifier under the Windows Boot Loader section next to the field name identifier.

• To check if the boot log entry is disabled or enabled, go check the “Bootlog” field under the Windows Boot Loader. And if it turns out that the “bootlog” entry is enabled, the entry will be “Yes”. Otherwise, the entry will be “No”.
• Next, type in the following command with the operating system identifier to enable the boot log.

bcdedit /set {identifier} bootlog Yes

Note: In the command given above, make sure that you replace the given system identifier with your computer’s system identifier. For instance: In this example, the identifier was replaced with the actual operating system identifier as current.

bcdedit /set {current} bootlog Yes

• Afterward, restart the system to start the Boot log process.
• After the restart, go to C:Windowsntbtlog.txt to open the boot log.

Note: Every time you restart your computer, the boot log file will keep on updating which will increase the size of the log eventually. So if you want seamless and easier troubleshooting, it is advised to disable the Boot log after you troubleshoot. To disable it using the Command Prompt, here’s what you have to do. Disable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• Once the Command Prompt is opened, type in the following command and then tap Enter to disable the boot log feature.

bcdedit/ set {identifier} bootlog No

Note: In the command given above, you need to replace the given system identifier with your computer’s system identifier. For instance: In this example, the {identifier} was replaced with the actual operating system identifier as {current}.

bcdedit /set {current} bootlog No

• Now close the Command Prompt.

Microsoft just released Windows 11 Insider build 22000.71. Let’s dive in and see what it brings with you.

Changes and features

New entertainment widget. The entertainment widget allows you to see new and featured movie titles available in the Microsoft Store. Selecting a movie will direct you to the Microsoft Store to see more information about that title. Just open widgets and click or tap on the “Add widgets” button and choose the entertainment widget. For now, the entertainment widget is available for Insiders in the following countries: US, UK, CA, DE, FR, AU, JP. The new context menus and other right-click menus have been updated to use acrylic material. We are testing the usability of a SplitButton for making new folders and files in the File Explorer command bar. The Taskbar previews (when you mouse-over open apps on the Taskbar) have been updated to reflect the new visual design of Windows 11.

Fixes

Taskbar:

• We fixed an issue where if you drag app icons on the Taskbar to rearrange them, it was making the apps launch or minimize when you released the icon.
• Using a long press with a touch on an app icon in the Taskbar to open the jump list should now work.
• After right-clicking the Start icon in the Taskbar, clicking somewhere else should now dismiss the menu more reliably.
• Shift + Right-click on an app icon in the Taskbar will now bring up the window menu like it used to and not the jump list.
• We’ve addressed an issue that was making your mouse move slowly when hovering over the Taskbar previews.
• We’ve included the fix for an issue when using multiple Desktops where an app icon in the taskbar might give the appearance of multiple windows being open when that wasn’t the case on that Desktop.
• When using the Amharic IME you should no longer see an unexpected X next to the IME icon in the taskbar.
• The issue where if you click on the input indicator on the Taskbar and it would unexpectedly highlight Quick Settings has been fixed.
• When you hover over Task View, the preview flyout for your Desktops will no longer pop back up after using Esc to dismiss them.
• We made a fix to address an issue where explorer.exe might crash after hovering over the Task View icon in the Taskbar.
• We fixed an issue where the selected date in the calendar flyout was out of sync with the date in the Taskbar.
• We made an update to address a scenario resulting in some Insiders not seeing the lunar calendar text in the calendar flyout when enabled in Settings.
• This flight addressed an issue that could unexpectedly make the Taskbar background transparent.
• Right-clicking the focus assist icon in the taskbar should now show a context menu.
• The issue from the previous flight where icons in the taskbar corner were getting crushed against the top of the Taskbar has been addressed.
• The tooltip for the location in use icon in the Taskbar should no longer appear blank sometimes.

Settings:

• We fixed an issue making Settings crash on launch periodically.
• Using the volume mixer sliders in Sound Settings should be more responsive now, as well as the page responsiveness as a whole.
• We fixed an issue resulting in Disk and Volumes Settings’ change size option being clipped.
• There was a non-functional verify link under Backup Settings – this has been fixed.
• The Power and Battery Settings page should no longer be reporting that the battery saver is engaged if it’s not.
• The Power and Battery Settings page should also now not crash when launched from Quick Settings.
• We fixed a grammatical error in the Sign-in Settings text.
• The “I forgot my PIN” link was unexpectedly missing in Sign-in Settings when a PIN was set up and has now been returned.
• The issue where the Move option under Apps & Features in Settings wasn’t working reliably should be addressed in this build.
• We’ve mitigated a problem where some of the colors in Settings weren’t updating after switching between dark and light mode, leaving the unreadable text.
• We’ve done some work to help improve the performance of Settings when switching between light and dark mode.
• We addressed an issue where some of the elements of the Themes page in Settings would end up crowded together when the window size was small.
• We resolved an issue where the Pen menu toggle under Taskbar Settings was not in sync with the actual state of the feature.
• Changes made to “Dismiss notification after this amount of time” in Accessibility Settings should now persist.
• Some of the icons you could enable in Taskbar Settings were erroneously labeled Windows Explorer even though that’s not what they were – this should now be fixed.
• The Connect text in Quick Settings has been updated to say Cast.

File Explorer:

• Clicking the command bar button twice should now close any dropdown that appeared.
• The new command bar should now appear when “Open folders in a separate process” is enabled under File Explorer Options > View.
• This build addresses an issue where right-clicking a file and selecting Open With > Choose another app might launch the file in the default app rather than opening the Open With dialog.
• Fixed an issue the desktop and File Explorer context menu would stop launching.

Search:

• We fixed an issue where the option to verify your account in Search wasn’t working.
• Hovering over the Search icon on a secondary monitor will now show the flyout on the correct monitor.
• Search should now work if you open Start and start typing after having gone to the apps list and back.

Widgets:

• When using the Outlook client with a Microsoft account, Calendar, and To-Do updates should sync faster down to the widgets.
• We addressed an issue where if you added multiple widgets quickly from the widget's settings, it could result in some of the widgets not being visible on the board.
• We fixed a bug where widgets could all become stuck in a loading state (blank squares in the window).
• The traffic widget should now follow the Windows mode (light or dark).
• The title of the sports widget should no longer mismatch with the content of the widget.

Other:

• This build addresses an issue where ALT + Tab was getting stuck open sometimes after you released the keys and had to be manually dismissed.
• We made a fix for an issue where Narrator's focus wasn’t ending up on the emoji panel after using the keyboard shortcut to open it.
• Magnifier’s lens view has been updated so the lens now has rounded corners.
• We found an issue that was noticeably impacting Start launch reliability for some Insiders, and have addressed it with this flight.
• We’ve updated the “Most Used” text in the Start menu’s app list so it should no longer be getting clipped.
• Using the semantic zoom in Start’s app list should no longer result in the list being pushed down and to the right off the edge of the window.
• We fixed an issue where if you pressed ⊞ WIN + Z you would need to press Tab before you could use the arrow key to navigate through the snap layouts.
• We addressed an issue where an acrylic area could get left on the screen after repeatedly snapping and unsnapping a window with touch.
• We’ve done some work to mitigate an unexpected flash when moving a snapped window with touch.
• We made a change to help window borders have a little more contrast when “Show accent color on title bars and windows borders” was turned off.

Known issues in Windows 11 repaired

Start:

• In some cases, you might be unable to enter text when using Search from Start or the Taskbar. If you experience the issue, press ⊞ WIN + R on the keyboard to launch the Run dialog box, then close it.
• Based on feedback, we are working on adding access keys to ⊞ WIN + X so that you can do things like “⊞ WIN + X M” to launch Device Manager. Insiders may see this functionality in this build, however, we are currently investigating an issue in which sometimes the option is unexpectedly unavailable.

Taskbar:

• There is an issue in this build where Explorer.exe will crash when the date and time button on the Taskbar is clicked to access new notifications with Focus Assist turned off. The workaround for this is to enable Focus assist to priority or alarms mode. Note that when focus assist is turned on, notification popups won’t appear, but they will be in the notification center when opened.
• The Taskbar will sometimes flicker when switching input methods.
• Taskbar previews may draw partially offscreen.

Settings:

• When launching the Settings app, a brief green flash may appear.
• When using Quick Settings to modify Accessibility settings, the settings UI may not save the selected state.
• The button to rename your PC doesn’t work in this build. If needed, this can be done using sysdm.cpl.
• Settings will crash when clicking “Facial recognition (Windows Hello)” under Sign-in Settings if Windows Hello is already set up.
• Reset this PC and Go back buttons in Settings > System > Recovery does not function. Reset and rollback can be accessed from the Windows Recovery Environment by selecting System > Recovery > Advanced startup, and pressing Restart now. Once in Windows Recovery, choose Troubleshoot.
• Choose Reset this PC to perform a reset.
• Choose Advanced options > Uninstall Updates > Uninstall latest feature update to perform a rollback.

File Explorer:

• exe crashes in a loop for Insiders using the Turkish display language when the battery charge is at 100%.
• When right-clicking the desktop or File Explorer, the resulting context menu and submenus may appear partially off-screen.
• Clicking a desktop icon or context menu entry may result in the wrong item being selected.

Search:

• After clicking the Search icon on the Taskbar, the Search panel may not open. If this occurs, restart the “Windows Explorer” process, and open the search panel again.
• When you hover your mouse over the Search icon on the Taskbar, recent searches may not be displayed. To work around the issue, restart your PC.
• The search panel might appear black and not display any content below the search box.

Widgets:

• Widgets board may appear empty. To work around the issue, you can sign out and then sign back in again.
• Launching links from the widgets board may not invoke apps to the foreground.
• Widgets may be displayed in the wrong size on external monitors. If you encounter this, you can launch the widgets via touch or WIN + W shortcut on your actual PC display first and then launch on your secondary monitors.

Store:

• The install button might not be functional yet in some limited scenarios.
• Rating and reviews are not available for some apps.

Windows Security:

• Device Security is unexpectedly saying “Standard hardware security not supported” for Insiders with supported hardware.
• “Automatic sample submission” is unexpectedly turned off when you restart your PC.

Localization:

• There is an issue where some Insiders may be missing some translations from their user experience for a small subset of languages running the latest Insider Preview builds. To confirm if you have been impacted, please visit this Answers forum post and follow the steps for remediation.

That's is so far, the latest update information on Windows 11 insider build. Stay tuned for more information when it comes as it comes.

As you know, storage devices are an important part of the computer system for porting, saving, and extracting data files. And for you to differentiate between storage devices on your computer system, each one of the storage devices is labeled with a unique number referred to as Disk Signature for identification. The unique disk identifier is stored as a part of the MBR or Master Boot Record. Disk signature is used by operating systems in order to identify and set apart different data storage devices and hard disk drives in the computer for data access. These days, Disk cloning has become a regular practice in upgrading to larger hard disk drives. Drives are cloned in order to produce a similar copy to use both the original drive and cloned copy together. Moreover, lots of virtualization tools are being used to virtualize the physical hard disk drives to create virtual hard disk drives and several virtual machine clones that are created with the existing virtual hard disk drives. And since these are identical copies, chances these copies may have identical disk signatures. As a result, when you use both disks that have identical signatures at the same time you run into the Disk Signature Collision problem. This kind of problem does not often occur as the Windows system does not really allow two disks to function simultaneously when they have the same disk signature. When you encounter a Disk Collision problem in your Windows 10 computer, you may see the following error messages:

• The boot selection failed because a required device is inaccessible
• The disk is offline because it has a signature collision
• This disk is offline because it has a signature collision with another disk that is online

You can fix the disk collision problem by changing the disk signature which you can achieve using the command line utility diskpart in Windows PowerShell or Command Prompt or using Windows Disk Management utility. To fix the disk collision problem, you can make use of the command-line utility called diskpart in Windows PowerShell or Command Prompt to view and change the signature, or can make use of Master Boot record in the Windows Registry. You can also make use of Windows Disk Management Utility to change the signature. Simply follow the given options below to change the disk signature either way.

Option 1 – Change Disk Signature via Diskpart

• Type “command prompt” in the Windows Search bar and then right-click on the related search result and select the “Run as administrator” option.
• After that, type the “diskpart” command and hit Enter to open Diskpart.
• Next, type the “list disk” command to display all the disks available in the system.
• Next, take note of the problematic disk number with the status Offline from the list and then type the “Select disk x” command where x is the offline disk to select the offline disk. For instance, if you type “select disk 1”, it will display the “Disk 1 is now the selected disk” message.
• Now type the “Uniqueid disk” command to display the disk signature and to change the disk’s signature and set the disk online, type the “unique disk ID= (New signature)” where (New signature) is the new ID in hexadecimal. For instance, you can set the new id as “unique disk ID= 1456ACBD”.

Note: If you have given the wrong format ID, the command prompt will display the following error:

“The specified identifier is not in the correct format. Type the identifier in the correct format: in hexadecimal form for an MBR disk or as a GUID for a GPT disk.”

• After you’re done, the disk will be online, and then restart your computer.

Option 2 – Change Disk Signature via Disk Management Utility

• Tap the Win + R keys to open the Run dialog box and then type “diskmgmt.msc” and hit Enter or click OK to open Disk Management.
• Next, right-click on the disk that is marked as Missing or Offline.
• After that, select the Online command from the drop-down menu.
• Then from the selecting option Online, Windows will generate a new disk signature.

If you receive an error message that says, “Entry point not found, The procedure entry point could not be located in the dynamic link library” on your Windows 10 PC, then you will find this post useful for this will provide you some potential fixes to fix the error. This kind of error can occur if a program fails to locate the DLL library that it needs in order to run. It can also occur if the library is not in the specified directory in the path or if the DLL file has gone missing or has become corrupted. To fix the “The procedure entry point could not be located in the dynamic link library” error, check out the following options given below.

Option 1 – Try to reinstall the program

The first thing you can do to resolve the error is to uninstall the program that throws the error and download its latest version from its official site and then install it again.

Option 2 – Run System File Checker scan

If reinstalling the program didn’t work, you can also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys 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.

 Reboot your computer.

Option 3 – Try checking the details in the Event Viewer

The Event Viewer can also help you resolve the error as it contains detailed information about the error that could help you pinpoint its root cause and resolve it.

Option 4 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) controls in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
  • exe /[DLL file]
  • exe [DLL file]

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 5 – Try to replace the DLL file with a trusted source

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:/Windows/System32
  • x64: This PC > C:/Windows/SysWOW64
• Next, type “cmd” in the Cortana search box and right click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 ntdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 6– Try to scan your computer using Windows Defender

It is also possible that the DLL file might be infected with malware or virus which could explain why you’re getting the error. Thus, you have to scan your computer using security programs like Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

There are cases when your Windows 10 PC can encounter an issue where it gets stuck and will display a message that says, “Preparing Security Options”. If this is happening to your Windows 10 PC, you won’t be able to use your keyboard or even mouse and your screen will only be stuck on the screen as mentioned above. As your computer is still stuck, you will be left with no choice but to shut it down and restart it. Tap the F11 key as soon as your PC powers on. This will take you to the Advanced Startup options where you can carry out some steps. If it still didn’t work, you have to boot your Windows 10 PC into Safe Mode and then try out the troubleshooting options below.

Option 1 – Try using System Restore

You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 2 – Uninstall the Windows Updates you’ve installed recently

The issue could be caused by Windows Updates so you need to check if it’s indeed the case. The best way you can do so is via Safe Mode.

• Boot your PC into Safe Mode and then tap the Win + I keys to open Settings.
• After that, click on Update and Security and then select Windows Update from the left side menu column.
• Next, select the “View installed update history” option on the right-side column and click on Uninstall Updates which will open a window that will show the list of all the installed updates on your PC.
• From there, select the update you want to uninstall and click the Uninstall button located in the lower right corner of the window.

Option 3 – Try disabling the Fast Startup

• Boot your PC into Safe Mode.
• Then tap the Win + R keys to open the Run dialog box.
• Next, type in “control” to open Control Panel.
• After that, select Hardware and Sound and click on Power Options.
• Select “Choose what the power buttons do” from the left side menu pane and click on Change settings that are currently unavailable.
• Afterward, uncheck the “Turn on fast startup (Recommended)” entry and click on Save Changes.
• Now restart your PC and check if the problem’s fixed.

Option 4 – Try running both the SFC scan and CHKDSK utility

You can do both SFC and CHKDSK using Safe Mode and Advanced Startup options. For Advanced Startup options, click on the Command Prompt option and proceed with the steps. And if you have booted your computer into Safe Mode, follow these steps:

• Tap the Win + X keys or right-click on the Start button and click Command Prompt (admin).
• After that, type in this command and tap Enter to run the System File Checker or SFC – “Sfc /scannow”.
• Alternatively, you can use this command instead if the previous command didn’t work – “sfc /scannow /offbootdir=c: /offwindir=c:windows”.
• Wait until the SFC scan is done with the process and then restart your PC.
• Next, run the CHKDSK utility and once it’s done checking your disk for errors and then reboot your PC to save the changes made.

Option 5 – Try resetting Windows 10

You can reset your Windows 10 PC using either the Advanced Startup Options or by booting into Safe Mode.

• Tap the Win + I keys and go to Update and Security > Recovery.
• Then click on Get Started under the Reset this PC section.
• After that, follow the on-screen instructions with how you want to reset your PC and what files and settings you want to revert.
• Then it will reset your PC by reinstalling it

Option 6 – Try to rename the SoftwareDistribution folder

In this option, the Command Prompt is supposed to be like the one in option 4. You can use both ways there to open the Command Prompt.

• Open an elevated Command Prompt as admin and type in the commands below and tap Enter right after you typed in each one of them
• net stop wuauserv
• net stop bits
• rename c:windowsSoftwareDistribution SoftwareDistribution.bak
• net start wuauserv
• net start bits

Note: You can also rename the SoftwareDistribution folder to “SoftwareDistribution.bak” or “SoftwareDistribution.old” after you boot your PC into Safe Mode.

Option 7 – Try rebuilding BCD

Rebuilding the BCD can help you in fixing the stuck Windows 10.

• 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.
• Next, select Command Prompt and type in the commands below one by one, and tap Enter right after you do so.
• exe /FixMbr
• exe /FixBoot
  • exe /RebuildBcd

Error Code 28- What is it?

The error code 28 is a driver error. This is one of the many device manager error codes. When this error occurs on your computer, the following message is displayed:

“The drivers for this device are not installed. (Code 28)”

Another driver device error message you might encounter is error code 41. 

Error Causes

Error 28 occurs because of unsuccessful device driver installation. This usually happens when you try to update new drive versions on your system. It is advisable to repair this error right away as it can hamper your ability to use certain hardware. For example, if error 28 occurs due to the unsuccessful installation of the USB driver, then it if not fixed and resolved it may prevent you from using hardware devices. Unsuccessful driver installation means you either didn’t install it properly or your computer has registry issues. If it’s the registry then you must fix it without any delay because it can expose your PC to serious threats like system crash and failure. To avoid such inconvenience, repair it.

Further Information and Manual Repair

When it comes to repairing the error code 28, here’s what you can do: Simply go to the control panel and click on the Device Manager option:

• In the details pane with the list of devices, locate the device for which you want to reinstall the driver software.
• Double click on it to open the properties dialog box.
• Now click on the driver tab and then click update driver.

After updating, try using that device again if it doesn’t work and shows the error code 28 on your computer screen then this means the underlying cause is the registry.

If you always use Google Chrome when browsing the internet, then you might have come across an error saying, “This webpage is not available, DNS PROBE FINISHED BAD CONFIG”. If you do, then this problem certainly has something to do with the DNS since any error code which has “DNS” in it points out a network issue in the computer. Getting the DNS_PROBE_FINISHED_BAD_CONFIG error indicates that your computer is not able to connect the website because the Domain Name Server or DNS wasn’t able to resolve the website name into IP address or it is not available at all. So in this guide, we’ll help you sort out this issue in Chrome on your Windows 10 PC.

Option 1 – Check the Network Cables and restart your router then reconnect

The most obvious thing you can do first is to try checking if the network cables connected to your computer or router are properly connected or not. If it turns out that some network cables are not connected properly, then it’s probably why you’re getting the DNS_PROBE_FINISHED_BAD_CONFIG error in Chrome. And if your computer is connected via Wi-Fi, you need to make sure to restart your router once. In addition, you can also forget the Wi-Fi your computer is currently connected to and then try reconnecting again to see if it would work.

Option 2 – Flush the DNS and reset TCP/IP

Flushing the DNS and reset TCP/IP could also help in fixing the DNS_PROBE_FINISHED_BAD_CONFIG error in Chrome. To do so, refer to these steps:

• Click the Start button and type in “command prompt” in the field.
• From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After opening Command Prompt, you have to type each one of the commands listed below. Just make sure that after you type each command, you hit Enter
  • ipconfig /release
  • ipconfig /all
  • ipconfig /flushdns
  • ipconfig /renew
  • netsh int ip set dns
  • netsh winsock reset

After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.

Option 3 – Try to remove the Proxy

You can also try to remove the Proxy as it might also help you in fixing the DNS_PROBE_FINISHED_BAD_CONFIG error. Here’s how you can do it:

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Option 4 – Change the DNS

Try to use the Google Public DNS If the first option didn’t work, you can try to use the Public DNS by Google and see if it can help fix the DNS error. You have to modify the DNS settings in your system explicitly and use the DNS IP addresses.

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8” and “8.8.4.4” and click OK and exit.

Option 5 – Clear Chrome’s browsing data

If your browsing data in Chrome hasn’t been cleared for some time now then that might be the reason why you’re suddenly getting the DNS_PROBE_FINISHED_BAD_CONFIG error when you browse the web. To fix this error, you need to clear your web browsing data. Refer to the following steps to do so.

• Tap the Ctrl + Shift + Delete buttons to go to the Clear browsing data section in Chrome.
• Next, set the time range to “All time” and tick all the boxes and then click on the Clear data button.
• After that, restart the Chrome browser and try to open the website you were trying to open earlier.

Option 6 – Try running the Chrome Cleanup tool

In case you don’t know, there is actually a built-in malware scanner and cleanup tool in Chrome that helps you get rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and other things that could affect the performance of the browser.

Receiving a screen of death is not a pleasant experience at all and most users would agree that they would very much like not to face one during their work with the computer. Sadly PC is not a perfect machine and it is not working in a perfect environment so errors happen. The most famous and well-known death screen is blue which is also the most common one, my bet would be that there is not a user which has not been faced with this blue error screen. There is no simple explanation why these stop errors occur as several factors can be involved. However, it is known that the malfunctioning of hardware drivers or drivers that are installed by third-party software drive this unwanted change. But did you know that there is more colors for infamous death screens and not just blue one? Microsoft has coded different errors to different colors in the goal for the technical team to be aware right away of what type and kind of error they are dealing with. Color for screen errors are: Blue, Black, Pink, Brown, Yellow, Red, Orange, Green and White If you are interested in what color represents what keep reading.

BLUE

A stop error or exception error commonly called the blue screen of death (BSoD) or blue screen, is an error screen displayed on Windows computers following a fatal system error. It indicates a system crash, in which the operating system has reached a condition where it can no longer operate safely. This is caused by many different problems, such as a general hardware failure or a crucial process terminating unexpectedly.

---

BLACK

On Windows 10 systems, a Black Screen of Death can be caused by an unfinished Windows Update. To resolve this problem, simply hold the power button down on your PC or laptop to switch off the computer. A cold start should result in the system booting properly.

---

PINK

It is a diagnostic screen with a white type on a pink background. Pink Screen is mainly seen when the VMkernel of an ESX/ESXi host experiences a critical error, becomes inoperative, and terminates any virtual machines that are running. It is not fatal and generally considered more of a developer testing issue. When encountered, it can be fixed quickly by following the simple action of pressing and holding your computer’s power button to shut down the device.

---

BROWN

The Microsoft Windows 10 Operating System Brown Screen of Death is an on-screen fatal error notification with bug check codes which is seen when a computer crashes due to graphics hardware or software-related problems (failing graphics drivers).

---

YELLOW

It affects the functioning of a browser, particularly Mozilla Firefox. The Yellow Screen of Death makes the appearance with a weird buzzing sound in the background when the XML parser refuses to process an XML document causing a parsing error and a weird buzzing sound. The issue persists unless the computer is manually rebooted.

---

RED

Commonly the Windows 10 red screen is caused due to the hardware error, particularly if you overclock your Windows PC/laptop. Despite this, sometimes the red screen of death is also caused by outdated or incompatible drivers or due to BIOS issues.

---

ORANGE

The Orange Screen of Death on Windows occurs due to fatal hardware errors. Multiple reasons have been reported for the Orange Screen of Death. Some had this issue when watching a YouTube video, some were not able to boot into Windows. It can even occur when waking up from Sleep.

---

GREEN

The green screen of death only appears when you're running an Insider Preview version of Windows 10. It's the same as the blue screen of death, and it will show the same error messages. ... If you see a green screen of death (GSOD) on your PC, that's a sign you're using an Insider Preview build of Windows 10.

---

WHITE

The White Screen on Windows is also an error where the screen of the computer just turns white and freezes. There can be several things that can cause the white screen to appear on the Windows laptop monitor. But the main issue could be because of malfunctioning of the graphics hardware.

When Windows 11 update is available but you do not wish to restart right away because you are in the middle of using a computer, you can schedule a restart for up to 7 days. It is very easy and we will show you how to do it.

1. Press ⊞ WINDOWS + I to open settings
2. Click on Windows Update
3. At the top, under the Restart required to click on Schedule the Restart
4. Click the switch under Schedule a Time to turn it ON
5. Use the Pick a Time and Pick a Day menu to set time and day when you want to update
6. Go back to one screen and visually confirm that the date is set
7. Close the settings

The scheduled restart will be confirmed in a message on the Windows Update page.

0x800ccc7d - What is it?

0x800ccc7d is an SSL (Secure Sockets Layer) error message code that occurs in applications like Microsoft Outlook or Outlook Express. The error message is displayed as: ‘ unknown error 0x800ccc7d- secure sockets layer ’. Many offices use Microsoft Outlook for email communication and sending instant messages within the office. This is a highly functional application that enables users to interact with peers efficiently, manage contacts, journals, and reminders. However, the error 0x800ccc7d may hamper your ability to send and receive emails efficiently. Therefore it is advisable to repair it right away.

Solution

Error Causes

The error 0x800ccc7d is triggered by the following causes:

• Damaged profile in Outlook
• Incorrect email account settings
• The Outlook installation is corrupt and damaged. This usually happens due to issues in hard disk storage.
• The outgoing SMTP server does not support secure connections

Further Information and Manual Repair

If you come across 0800ccc7d error code while using Microsoft Outlook or Outlook Express, then don’t you worry! This problem can be easily resolved. In fact, it is so easy to repair that you can do it by yourself even if you are not a technical expert. Here are some ways to fix the 0800ccc7d SSL Outlook error:

Solution 1: Use Scanpst.exe

You may not know this but Microsoft offers an inbuilt Outlook Repair tool. This tool is technically known as Scanpst.exe. This tool is useful when you need to repair Basic header corruption. However, it may not be the best choice if the problem is big and complex.

Solution 2: Reset Your Outlook Settings

Sometimes this error message may occur when the STMP server requires authentication or does not recognize the senders' email addresses. In this scenario, you should check your Outlook settings to make sure that your STMP username and server are correct. For this follow this procedure:

• Go to the Tools menu and then click on Accounts
• Now click on your email account then check its properties
• Click general and make sure that your email address is created in your account’s control panel. If not, then edit and create.
• Next, click servers and see if the box next to the option that says My server requires authentication is checked or not. If not, then check it to resolve the error.

Solution 3: Disable any Anti-Virus

Another alternative to resolve this error is to disable any Anti-virus or Firewall you have installed on your PC. Once you disable it then try sending or receiving the email again. This usually works.

Solution 4: Download 0x800ccc7d Repair Tool

The fourth solution available to resolve this issue is by downloading the 0x800ccc7d repair tool. Though it is similar to Microsoft Outlook built-in scanpst.exe tool, but as compared to it the 0x800ccc7d repair tool is a highly functional tool. There are many 0x800ccc7d repair tools available but we recommend you to Restoro. This tool is a third-party tool that can deal, scan, and fix 0x800cc7d error in no time. What makes this repair tool an excellent choice is that it can repair all broken PST files and emails, recover Outlook items, retrieve deleted files, recover password-protected data, split files to recover oversize PST files, and more. To access and install the 0x800ccc7d repair tool all you need to do is download it here and install it on your PC. Now run it to scan errors. Once the errors are scanned, hit the repair tab to resolve. So, next time when you experience the error 0x800ccc7d, try using these solutions to fix the problem right away!