Logo

Moving Taskbar to second monitor in Windows

If you are using a multi-monitor, then you might find it quite useful. It helps many users with their work and brings more productivity. And over the past few years, Windows has managed to offer one of the excellent multi-monitor features where users can plug in an additional monitor and access their work or use their computer seamlessly on both displays. This is really handy, especially for users who are graphic designers, gamers, and other professionals who have to use a larger screen for their work.

One of the biggest inconveniences for users who use multi-monitor is that the Taskbar is switched on, on both displays, by default. This default arrangement is most likely to cause clutter on the second display. So if you are one of these users who find such a thing annoying, then you will find this post useful for you as we will walk you through how you can move the Taskbar to a second monitor. To get started, follow the instructions laid out below.

Step 1: The first thing you have to do is right-click on the Taskbar.

Step 2: Next, uncheck the “Lock the taskbar” option.

Step 3: After that, click and hold the taskbar and drag it to the second monitor.

Step 4: Once done, click the mouse button on the place where you want to place the taskbar.

Step 5: Now right-click on the “Lock the taskbar” option to lock the taskbar.

Once you’re done carrying out the steps given above, there are Advanced Options you can explore. This array of advanced options are offered by Windows 10 to fine-tune the multi-monitor experience of users. For instance, you have the option to choose to show the taskbar on an active screen only or combine the buttons on other taskbars. It would be better if you try out different variations and stick with the best one. In addition, you could also move the taskbar from one display to another.

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

Fix DRIVER_CORRUPTED_EXPOOL Error
If you suddenly encounter the DRIVER_CORRUPTED_EXPOOL Blue Screen of Death error when using your computer, then there might be some issues with the device drivers on your Windows 10 computer. This kind of BSOD error can occur at any point while you are using your PC. Its main cause is due to some error in the System Pool where a driver becomes incompatible with the operating system or when the configuration files get corrupted for some reason. If you are one of the users who are currently inconvenienced by the DRIVER_CORRUPTED_EXPOOL error, worry not, as this post will give you some potential fixes that might help resolve the problem.

Option 1 – Perform a System Restore

Performing System Restore might help you in fixing the DRIVER_CORRUPTED_EXPOOL Blue Screen error. 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 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like DRIVER_CORRUPTED_EXPOOL error. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:
  • Tap the Win + I keys to open the Settings panel.
  • Then go to Update & Security > Troubleshoot.
  • From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 3 – Update the Device drivers

The device driver installed in your computer might be incompatible with your operating system which is the reason why the DRIVER_CORRUPTED_EXPOOL Blue Screen error occurs. To fix that, you have to update your device drivers.
  • Tap the Win + R keys on your keyboard to open the Run dialog box.
  • After that, type “msc” in the field and hit Enter or click OK to open the Device Manager.
  • After opening the Device Manager, update all the outdated Device drivers on your computer.
  • Next, right-click on all the driver entries that are appropriately labeled, and then click the Update driver option.
  • Now restart your PC and check if the BSOD error is fixed or not.

Option 4 – Uninstall any faulty device drivers

  • Tap the Win + R keys on your keyboard to open the Run dialog box.
  • After that, type “msc” in the field and hit Enter or click OK to open the Device Manager.
  • From there, look for any device driver which has a yellow exclamation mark which indicates that something is wrong with them.
  • And then right-click on each one of them and click on Uninstall.
  • Once you’re done uninstalling the faulty drivers, restart your computer and allow your computer to reinstall the drivers you just uninstalled.

Option 5 – Try running the System File Checker

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 that might be causing the Machine Check Exception BSOD error. 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.

Option 6 – Try updating the BIOS

As you know, the BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “msinfo32” in the field and press Enter to open System Information.
  • From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
  • After that, you should see the developer and version of the BIOS installed on your PC.
  • Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
  • If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
  • Now double click on the downloaded file and install the new BIOS version in your computer.
  • Now restart your computer to apply the changes made.

Option 7 – Try resetting Windows 10

To fix this BSOD error, you can try resetting Windows 10. Doing so won’t get rid of any file in your system – instead of erasing all your media files and documents, this reset option resets all the system settings and files.
Read More
Fix The driver detected a controller error
One of the worst problems users can encounter on their computers is Blue Screen of Death errors as some of them are quite hard to fix. One of them is the “The driver detected a controller error” Blue Screen error. It could be followed by “DeviceIdeIdeport0 OR”, “on deviceharddisk0dr0”, or “DR3” or the name of the drive or port that’s causing the problem. If you are one of the users who encountered this error, then the suggestions provided in this post would definitely help you in fixing the problem.

Option 1 – Try to disconnect and reconnect all hardware and cables

A lot of users reported that they were able to fix the problem by disconnecting and reconnecting cables and hardware like scanners, printers, cameras can help in fixing the problem. In addition, you can also boot your computer in a Clean Boot State so that you can find the problematic hardware by hit and trial method. Refer to the steps below to do so:
  • 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.)

Option 2 – Update the device drivers

Updating the outdated device drivers in your computer can also help in fixing the problem. To do so, refer to these steps:
  • First, boot your computer into Safe Mode.
  • After that, tap the Win + R keys to launch Run.
  • Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
  • After that, a list of device drivers will be displayed. From there, look for any outdated device drivers and click on each one of them.
  • After that, right-click on each entry of the device drivers and select the “Uninstall Device” option from the menu.
  • Now restart your computer.
  • After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Option 3 – Try to update the BIOS

Updating the BIOS can help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “msinfo32” in the field and press Enter to open System Information.
  • From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
  • After that, you should see the developer and version of the BIOS installed on your PC.
  • Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
  • If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
  • Now double click on the downloaded file and install the new BIOS version on your computer.
  • Now restart your computer to apply the changes made.

Option 4 – Try running the Blue Screen Troubleshooter

You might also want to run the Blue Screen troubleshooter. It is one of the built-in tools in Windows 10 that helps users in fixing system issues including Blue Screen errors. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:
  • Tap the Win + I keys to open the Settings panel.
  • Then go to Update & Security > Troubleshoot.
  • From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 5 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the “The driver detected a controller error” Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:
  • Tap the Win + R keys to open Run and type mdsched.exe and hit Enter to open the Windows Memory Diagnostic Tool.
  • After that, it will give two options such as:
    • Restart now and check for problems (Recommended)
    • Check for problems the next time I start my computer
  • Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.
Note: After you select your preferred option, your computer will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 6 – Replace your motherboard

If your computer is still under warranty, you should consider replacing your computer’s motherboard in case the options given above failed to work in fixing the Blue Screen error.
Read More
Make AI images on your local PC

Stable Diffusion is a machine learning model developed by Stability AI to generate digital images from natural language descriptions. The model can be used for different tasks like generating image-to-image translations guided by text prompts and upscaling images.

Unlike competing models like DALL-E, Stable Diffusion is open source and does not artificially limit the images it produces. Stable diffusion was trained on a subset of the LAION-Aesthetics V2 data set. It can run on most consumer hardware equipped with a modest GPU and was hailed by PC World as "the next killer app for your PC".

stable diffusion

Since Stable Diffusion is run locally and not in the cloud, as mentioned there is no limit to the number of images that you can produce but in order to use it you will have to get down a little dirty with setting your PC environment for it since it is not really an application, it is a command line text based descriptor that will use python to generate your images, so there is no install nor GUI.

In this guide, we will show you how to both install and run Stable Diffusion on your local PC so you can start producing some cool images all by yourself.

Hardware and software requirements

Make no mistake, Stable Diffusion will not run on a potato PC, in order to harvest the power of AI-generated imagery this is what you will need:

  • A GPU with at least 4GB of VRAM
  • 10GB of hard disk space
  • Python and libraries (Miniconda3 installer will install everything you need)
  • The Stable Diffusion files
  • Git
  • Any OS (Windows, Linux, macOS)

Installing components

For this tutorial, we are covering the installation and running of Stable Diffusion on Windows PC. The steps presented here are presented in a way that installation can be performed on any operating system but precise instructions will be for Windows OS.

GIT

The first thing to do is to install GIT. It is a tool that will let you easily maintain and install repos from the internet. to install it go to: https://git-scm.com/ and click on download. Follow the instructions for your version of the operating system. If you are a developer you are familiar with GIT and if you already have it installed you can skip this step.

One thing that is important when installing GIT locally is to select to use it via the command line (the second option that says "Git from the command line and also from 3rd-party software").

Miniconda3

Now when we have GIT installed, next thing is to use Miniconda3 to install python and all required libraries that are needed. Get the installer at: https://docs.conda.io/en/latest/miniconda.html

Miniconda3 is basically an easy installer so you do not have to install tons of stuff manually from different websites and sources, it is nicely packaged in the installer that will take care of everything.

Stable Diffusion

After the previous two steps, we are ready now to actually install Stable Diffusion. Go to https://huggingface.co/CompVis/stable-diffusion#model-access and install the latest library (as of the writing of this article currently it is stable-diffusion-v1-4-original, the last one on the right), the library is almost 5GB in size so be prepared for big download.

After installing stable diffusion's latest library it is time to update it to the newest version. You can download ZIP from GIT HUB https://github.com/CompVis/stable-diffusion

Once downloaded click on the Windows start button and type in Miniconda3 and click on open. Create a folder and name it how you want on a drive of your choice. For this example, we will install it all in disk C under folder AI_art, follow the instructions below but use your own names and destination instead. Do not close Minicoda3 after typing commands!!!

cd c:/
mkdir AI_art
cd AI_art 

Extract GitHub files that you have downloaded into your new folder and get back to Minicoda3 and type the next commands:

cd C:\AI_art\stable-diffusion-main
conda env create -f environment.yaml
conda activate ldm
mkdir models\ldm\stable-diffusion-v1

Let the whole process finish, some files are large and it might take a while. After the whole process is finished and completed, copy the checkpoint file that you have downloaded into: C:\AI_art\stable-diffusion-main\models\ldm\stable-diffusion-v1

After the file is copied rename it to model.ckpt and you are finished.

Running Stable Diffusion

The created environment is needed in order to actually use Stable Diffusion to create images. Each time you want to use it you will have to run it, so go into Miniconda3, and inside it type:

conda activate ldm
cd C:\AI_art\stable-diffusion-main

after we are inside the folder call the script with the parameters:

python scripts/txt2img.py --prompt "TXT DESCRIPTION OF IMAGE THAT YOU WANT TO CREATE" --plms --n_iter 5 --n_samples 1

and that's it, your image is created and it is located in C:\AI_art\stable-diffusion-main\outputs\txt2img-samples\samples

Read More
Problem running preinstall.cmd scripts
Setting up the Windows operating system in a computer can be quite a complicated task since there are a couple of things that take place in the background to ensure a full and protected setup of the operating system which includes a number of programs, scripts, and so on. They work together in the background to guarantee the integrity of the Windows operating system. However, there are times when this piece of code could also go wrong. As a result, you might encounter errors like the “There was a problem running preinstall.cmd scripts” error. “Preinstall.cmd” is a type of CMD file associated with Applications & Drivers developed by Gateway for the Windows OS. To fix the “There was a problem running preinstall.cmd scripts” error, there are several things you can try. You can try to download a new Windows installation image or create a new bootable drive as well as uninstall conflicting or incompatible programs. In addition, you can also run the Windows Update troubleshooter or reset Windows 10.

Option 1 – Try to download a new Windows installation image

Your first option to fix the “There was a problem running preinstall.cmd scripts” error is to download a new Windows installation image. You can get the official ISO files for the latest release of Windows 10. After you’ve downloaded the ISO files, you can use them to upgrade to the latest Windows 10 version.

Option 2 – Try creating a new bootable drive

  • Insert your USB drive into your PC.
  • Tap the Win + R keys to open the Run dialog box and type in “cmd” and tap Enter to open the Command Prompt. Alternatively, you can also search for “cmd” in the Cortana search box to open Command Prompt.
  • Once you’ve opened CMD, type in this command to open the DISPART utility – diskpart
  • After that, you should see a new black and white window that would say, “DISKPART>”.
  • Next, type in “list disk” in the command line and tap Enter to see the list of all the Storage devices as well as your hard disk connected to your PC. Here, you have to identify your disk’s number.
  • Type in this command where “X” is the disk number you have identified and then tap Enter – disk X
  • Type in this command and hit Enter to clear the table records and all the visible data on the drive – clean
  • Now you have to recreate a new primary partition of the drive so you’ll have to type in this command and tap Enter right after – create part pri
  • A new primary partition has been created so you have to select it by typing this command and tapping Enter – select part 1
  • Now you have to format it to make it visible to normal users by typing – format fs=ntfs quick
Note: If your platform supports the Unified Extensible Firmware Interface or UEFI, replace the “NTFS” with “FAT32” in the command on Step 10.
  • After that, type in this command and tap Enter after – active
  • Finally, type this command and hit Enter to exit the utility – exit
  • After you prepare the image for the operating system, save it to the root of your USB Storage device.

Option 3 – Try to uninstall conflicting programs

If you are using a computer made by Dell and got Windows 10 preinstalled in it, then you can try to uninstall the programs listed below and see if it fixes the problem.
  • Dell Encryption Management service
  • Dell Digital Library service

Option 4 – Run the Windows Update Troubleshooter

You might also want to run the built-in Windows Update Troubleshooter in Windows that could help you in resolving the “There was a problem running preinstall.cmd scripts” error. All you have to do is go to Settings > Update& security > Troubleshoot > Windows Update. From there, click on the Run the troubleshooter button and follow the next one-screen instructions that appear. After that, restart your computer and check if the error is now fixed or not by trying to install the update once again.

Option 5 – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the error. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically.

Option 6 – Try to reset Windows 10

  • Tap the Win key or click on the Start button located in the Taskbar.
  • Then click on the Power button at the bottom right portion of the screen.
  • Next, press and hold the Shift key on your keyboard and then click on Restart. This will restart your Pc into the Advanced Startup options.
Note: Once you have access to the Advanced Startup options, you have to go to the setting which allows you to Reset your Windows 10 PC. All you have to do is select Troubleshoot > Reset this PC to reach the following screen Afterward, select either the “Keep my files” option and then proceed to the next on-screen instructions that follow to reset your Windows 10 computer without losing your files.
Read More
Fix fatal device hardware error on Windows
This post will help you fix the request that failed due to a fatal device hardware error on your Windows 10 PC. You can encounter this error when that hard drive/SSD on your computer is damaged physically and the system is either unable to access or perform read/write operations in it. Aside from hard drive/SSD, this error can also happen to removable drives. This kind of error is not uncommon and in most cases, the hardware is physically damaged due to which you are not able to perform operations. However, there are a couple of fixes that you can try to resolve the problem before you go ahead and back up your data and move them to a different drive. What exactly causes this error? It’s actually self-explanatory and it gives you an idea that the drive is either corrupted or in a bad state. To resolve the error, follow the given options below carefully and see which one worked best for you.

Option 1 – Verify the hard drive using SMART attributes

In case you don’t know, Windows has a built-in feature of SMART analysis which analyzes the hard drive/SSD and checks all the parameters by performing some minor operations. To use it, follow these steps:
  • Tap the Win + S keys and type “command prompt” in the field then right-click on the related search result and select the “Run as administrator” option.
  • After opening Command Prompt as admin, type the “wmic diskdrive get status” command and hit Enter.
  • You should get a result after that, and if you see that it’s “normal”, proceed to the next option below.

Option 2 – Use the CHKDSK utility

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system.
  • Tap the Win + S keys to open the Search box.
  • Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
  • After opening an elevated command prompt, copy and paste the following command and hit Enter:
CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]
Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.
  • Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
  • If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
  • After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
  • Wait until the process is completed and then restart your computer.

Option 3 – Format your drive

You can try formatting your drive since this problem also occurs on removable hard drives. In addition, if your drive is not properly initialized, this error will really pop up. Thus, you need to make sure that the hard drive is initialized and that the correct partition style is selected.
  • To get started formatting your drive, tap the Win + E keys and then go to the access page of the drive.
  • Next, right-click on the drive and select Format.
  • After that, uncheck the “Quick Format” option and then format your drive properly.
  • Now once the formatting process is finished, unplug the drive and plug it back in afterward.
  • Check if the error is already fixed. If the drive is not initialized, tap the Win + R keys and hit Enter.
  • After opening the Run dialog box, type “diskmgmt.msc” and hit Enter to open Disk Management.
  • From there, right-click on the drive volume and select Initialize Disk.
  • Next, select the correct partition type and proceed.
That should fix the problem, if not, follow the next advanced option below.
Read More
Fix Boot Device Not Found 3F0 Error
Today we will be solving the Device not found 3F0 error which is a common error, especially among HP (HP Pavilion G6), Lenovo, Acer, and Dell laptops/desktops. This error occurs when the computer is turned ON and when the system is about to boot. It can happen on windows 7,  8, or 10. When a mentioned error occurs one of the following messages will be displayed on your screen:
  • “No bootable device – insert boot disk and press any key”
  • “No Boot Device Found. Press any key to reboot the machine”
  • “Boot Device Not Found. Please install an operating system on your hard disk. Hard Disk (3FO)”
  • “No boot device is available”

The most common reasons for 3F0 error to occur is:

  • Using the unbootable device or disk to boot from.
  • If the bootable hard drive you are using might have corrupted or damaged somehow.
  • MBR or boot sector is damaged on the bootable hard drive.
  • If your system has gone through a virus or malware attack.
  • The wrong boot order in the BIOS.
  • Hard disk connection problem.
  • System files or boot files unknowingly damaged.
  • Corrupt hard drive partitions.
Now all of these being said let us go through some of the solutions and fix this dreaded error in order to get your computer back in working order:

1: Change Boot Order


This is well, the most simple solution and the easiest one, try to change the boot sequence in the BIOS settings of your motherboard. Sometimes most easier solutions can provide great results and solve our problems. If sadly this fails and the issue persists move to the next solution.

2: Perform a Hard Reset


Performing hard reset can often solve issues, to perform a hard reset do the following:
  • Turn off the computer and unplug the power adapter. If there is a removable battery, it should also be removed.
  • Then disconnect all peripherals, including the removable hard drive, etc.
then
  • Press and hold the power button for 15 seconds to drain all remaining power.
  • Insert the battery, and then re-plug the AC adapter into the laptop.
  • Press the power button to turn on the computer.
  • Once the computer starts up properly and the startup menu appears, use the arrow keys to select “Start Windows normally” and then press Enter.
Reconnect everything back of your peripherals. If by any chance problem still persists follow the next step:

3: Test Hard Drive Using HP Diagnostic Tool


Use the built-in tool in the Hp device to solve the issue:
  • Turn on your computer and keep pressing the Esc key until the menu appears on the screen.
  • Next, press the F2 key.
  • Choose the Components Tests option from the HP PC Hardware Diagnostics menu.
  • Select Hard Drive from the Component Tests menu.
  • Click on the Quick Test, then click on the Run once button.
  • If there are still any issues with your hard drive, then run the Extensive Test.

4: Restore BIOS Default Settings


  • Press the Power button to start the computer, and immediately after this, repeatedly press the F10 key to enter the BIOS setup menu.
  • To load and restore BIOS Setup Default settings, press F9 on the BIOS setup menu.
  • Once loaded, press F10 to Save and Exit.
  • Select yes, and then press Enter when it says Exit Saving Changes.

5: Reconnect Your Hard Drive


  • Turn the computer off and remove the power cable.
  • If you have a removable battery, take it out
  • Disconnect your hard drive and then connect it back.
  • Reassemble your computer and turn the computer on to see if it fixed the issue.

6: Fix and Rebuild Damaged MBR


  • Boot from the original installation DVD (or the recovery USB)
  • At the Welcome screen, click Repair your computer.
  • Choose Troubleshoot.
  • Choose Command Prompt.
  • When the Command Prompt loads, type the following commands: bootrec /FixMbr bootrec /FixBoot bootrec /ScanOs bootrec /RebuildBcd.

7: Fix Operating System


  • Prepare a Windows installation disc, CD/DVD or USB flash drive and connect it to your PC.
  • During the installation process, launch Command Prompt.
  • In Windows 7, under the System Recovery Options tab, click Startup Repair.
  • In Windows 8 and Windows 10, click Repair your computer, then select Troubleshoot > Advanced options > Automatic Repair (Windows 8) or Startup Repair (Windows 10).

8: Replace the Hard Disk

Read More
Fix error 0x8007000d in Windows
Hello everyone and welcome to another quick tutorial for your Windows error, this time we will wrestle with error 0x8007000d.

Let's begin:

1. Browse to "C:\Windows\SoftwareDistribution\Download" and delete the contents of the folder. 2. Press ⊞ WINDOWS + X > Click Command Prompt (Admin) then type "wuauclt.exe /updatenow". Hit Enter 3. Open Control Panel > Windows Update and Windows 10 should begin downloading. Press ⊞ WINDOWS + X Click Command Prompt (Admin) Type in at the prompt OR Copy and Paste these one at a time : (Hit ENTER after each)
Dism /Online /Cleanup-Image /CheckHealth Dism /Online /Cleanup-Image /ScanHealth Dism /Online /Cleanup-Image /RestoreHealth
also

Run the Windows Update Troubleshooter and check if it helps:

  1. Press ⊞ WINDOWS + X and select the Control panel.
  2. In the search box, type troubleshooter, and then click Troubleshooting.
  3. Under System and Security, click Fix problems with Windows Updates.
Read More
Fix Error 0xe0434f4d

What is Error 0xe0434f4d?

Error 0xe0434f4d displays when a remote computer runs an instance of the SQL Server 2005 but it fails to initialize. When the plan is started, this error displays in a status window on the SQL Server. Also, when the Update-OffilineAddressBook cmdlet is started in Microsoft Exchange Server, this error can occur.

Solution

Restoro box imageError Causes

Error 0xe0434f4d can occur for possibly two main reasons. The first one is when the System Attendant Service is not properly running, and the second when you don’t have the permission to run the update. Other causes are when the .NET Framework 2.0 security does not allow sqlplanlaunch access to run from a shared network. Another cause is when the Offline Address Book (OAB) is not found in the Configuration Domain Controller server that the server of OAB generation uses.

Further Information and Manual Repair

In case you didn’t know, the Offline Address Book generation server is a mailbox server, and in order to resolve error 0xe0434f4d, you will have to replicate the OAB object to the Configuration Domain Controller server. In order to do so, follow steps:
  • Go to start and click on All Programs, then go and click on Microsoft Exchange Server 2010. Click on Exchange Management Console
  • In Exchange Management Console, go to Server Configuration and click on Mailbox
  • In the details, go to mailbox server that generates Offline Address Book and right-click it, then go to Properties
  • In the Properties, click on System Setting and locate the domain controller name in the box that reads Domain controller servers being used by Exchange
Make sure the OAB object is reproduced in the Configuration Domain Controller Server. Follow these steps to do that:
  • Go to Start and click on Run. Type Adsiedit.msc in Open box and press Enter. Right-click on ADSI Edit and click on Connect to
  • Locate a list reading Select a well-known naming context, and from there select Default naming context. In a Select or type a domain or server window, type FQDN (fully qualified domain name) of the Configuration Domain Controller server which was determined in step 1, and click OK
  • Expand Configuration [dc.domain.com], expand CN=Configuration, DC=domain, DC=com, expand CN=Services, expand CN=First Organization, and expand CN=Address Lists Container
  • Click on CN=Offline Address Lists and make sure the OAB object is listed on the details pane
When the OAB generation server receives this, then it will connect to the Configuration Domain Controller server and will locate the OAB object. If the OAB generation server is unable to find the OAB object, then the error will return on the cmdlet. On SQL Server, you should change the .NET permissions to allow sqlplanlaunch application access to run from shared administration. For that, follow these steps:
  • On ArchiveIQ Server, open System from the Control Panel and note down the computer name
  • On SQL Server, log in as administrator and open the command prompt
  • On the command prompt type, ‘C:windowsmicrosoft.netframeworkv2.0.50727caspol.ece –m –ag l – url file:\[Archive IQServer Computer Name]AlQRemote$*FullTrust and Press Enter. Type yes and press Enter again to confirm the permission changes.
Read More
Cannot start new hardware device, Error 49
In case you don’t know, the Windows Registry contains a System Hive which is a core part of Windows. The Windows operating system store various settings, options, and configurations. And if you encounter a Device Manager Error 49 for a device then it means that the system hive has exceeded its size limit. Worry not for this post will provide you with possible solutions that can help you in fixing error code 49. You will see the following error message when you encounter error code 49:
“Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit), (Code 49)”
There are instances when it may so happen that the device or devices are no longer attached to the computer but they are still listed in the system hive of the registry. For instance, if you were removing hardware and application for years but they weren’t removed from the registry then the size of the system hive keeps on growing until it hits the maximum limit. As you know, making changes in the registry manually, no matter how knowledgeable you are on such things is not sage since the registry is not only important but also complex. In addition, the System Hive is also a permanent part of the Registry associated with a set of files that contain information related to the configuration of the computer on which the OS is installed. To resolve this error, you must remove or uninstall any hardware devices that are no longer in the system. In fact, the Device Manager hides them by default so you need to enable hidden or non-present devices. Follow the instructions given below to set the Devices Manager to display devices that are no longer connected to the computer. Step 1: Tap the Win + R keys to open the Run dialog box. Step 2: After that type in “cmd” and hit Enter to open the Command Prompt. Step 3: Type “set devmgr_show_nonpresent_devices=1” in the Command Prompt and hit Enter to enable the hidden devices option. Step 4: After that, exit Command Prompt and tap Win + X + M to open the Devices Manager. Step 5: After opening the Devices Manager, click on View and then select the “Show hidden devices” option. This will show you all the devices that are not connected to the computer but are still mentioned. Step 6: Next, select a non-present device and click Uninstall from the Driver tab. Step 7: After that, repeat what you’ve done on step 5 for any other device that you no longer use. Step 8: Restart your computer. You can check the device Properties dialog box in the Device Manager after you’re done removing all the useless devices, to check if the error is now fixed or not. Moreover, you can also try running the Hardware and Devices Troubleshooter as it can also help resolve hardware-related problems. To use it, refer to the steps below.
  • The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
  • After opening Settings, look for the Update and Security option and select it.
  • From there, go to the Troubleshoot option located on the left-hand side of the list.
  • Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
  • After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.
Read More
See if your Data is safe in Facebook breach
It is no secret that a few days ago Facebook has been breach and tons of user accounts have been compromised. These kinds of things are very unpleasant experiences for both users and the company itself. User trust lowers significantly in the company and it can greatly increase the chances of users migrating to another platform. This just shows how much a hacker or security breach can produce damage to the business. Sadly we can not offer you guidance or assistance in recovering your stolen data nor can we provide you with removing your data from the hands of the attacker. What we can do is to provide you with information has your data been stolen. Threat actor released the personal information for 533,313,128 Facebook users on a hacking forum, including mobile numbers, name, gender, location, relationship status, occupation, date of birth, and email addresses. This data was originally sold in private sales after being collected in 2019 using a bug in the 'Add Friend' feature on Facebook. Facebook had closed this vulnerability soon after it was discovered, but threat actors continued to circulate the data until it was finally released practically for free. Since then, Troy Hunt has added the leaked data to his Have I Been Pwned data breach notification service to help users determine if a Facebook member's data was exposed in the leak. Go to the site and enter your email address to check and see if your data has been compromised.
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