Error 0x8007002C - 0x4001E, installation failed in the SECOND_BOOT phase

Originally Microsoft has imagined its widgets menu as Microsoft-only widgets but it seems that they have changed their mind. Due to the latest leak, it seems that Microsoft will open the widgets menu to 3^rd party developers as well but at launch, it will be only official widgets. It was hinted that later widgets menu will be open to developers who want to bring their own stuff into it. Distribution, date, and technology that will need to be used in order to create your widget have not been discussed nor leaked at a given time but in some way, I am very glad that at least some customization will be in Windows 11. It is funny and amusing how some things that were in Windows Vista are getting back like glass design, round corners, and widgets. Let’s just hope Windows 11 will be a better Windows than Vista was.

Google's Pixel smartphone is one if not the best Android smartphone on the market. It regularly gets updates and Google is really trying to keep it as a top choice for Android smartphone users. One of the new things that Google has released for its smartphone series is a new emergency dialer.

With an emergency dialer, you will be able to quickly access local contact information for police, fire, and medical services. This dialer is able to contact before mentioned services even when the phone is locked and when you are traveling.

The idea is to quickly access the default emergency number no matter in which country you are currently in, service will find the appropriate number and set it as default so if you need it there is no delay in searching for the appropriate number and dialing it.

Once the service is enabled on the device you can swipe up and tap Emergency call without unlocking your phone or you can press and hold the power button for five seconds and tap Emergency.

If you have a Pixel smartphone go to the Google support page and follow instructions on how to enable this service. It costs nothing and it could potentially even save your life.

There are times when you upgrade or install Windows 10 on an old computer and the Aspect Ratio of the screen is in a mess. This issue occurs when a new Windows version does not support the GPU or the driver does not work in Windows 10. And in such cases, Windows uses a generic driver which does not support all the resolution as well as the correct aspect ratio. So in this post, you will be guided on how you can fix the issues with the screen aspect ratio in Windows 10. It could be that your screen has an aspect ratio of 16:9 but after the upgrade, you changed to screen resolution, and is now set to 16:!0. And later on, you found that you are unable to go back to the previous aspect ratio. Thus, you will notice that everything on the screen might look stretched. You might be wondering if it’s possible to change the aspect ratio in Windows 10 directly even if the GPU does not have the compatible driver, well it really isn’t. However there is another way to resolve the problem. Refer to the options given below to get started.

Option 1 – Try using the Compatibility Mode

The first thing you can do is to run the driver in a Compatibility Mode. Follow the steps below to do so:

• You need to download the driver and place it on your desktop.
• After that, right-click on it and select Properties.
• Next, switch to the Compatibility tab where you should see two options:
  • Compatibility troubleshooter, and let Windows figure out what works best for you. If it fails, follow the next.
  • Manually choose the version of Windows it was correctly working.
• You also have the option to change the DPI settings and see if that helps. Then click the Apply and OK buttons.
• Now right-click on the file and select the “Run as administrator” option to install. After that, you should now be able to change your screen aspect ratio to what you were using early on.

Note: If you have other programs that won’t work on the existing version of Windows, then make sure to run the program in a Compatibility mode.

Option 2 – Try to run the Program Compatibility Troubleshooter

You might also want to run the Program Compatibility Troubleshooter. This built-in troubleshooter is available in the Windows Update & Security section. From there, select Troubleshoot. This will find a list of programs for you and since you have already downloaded the driver files, just click on Not Listed located at the top of the program list. After that, browse and select the driver files and then let the program do its job.

Option 3 – Update or rollback your device drivers

If the first option didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

What is Mapi32.dll Outlook Error?

Mapi32.dll is a Windows Messaging Application Programming Interface that enables Windows to perform various email functions and launch messaging programs like Microsoft Outlook and Microsoft Office. The inability of the interface to execute email functions properly results in the Mapi32.dll Outlook Error. This error occurs mostly when you are attempting to upgrade the operating system to a new version.

Solution

Error Causes

The common causes of the Mapi32.dll Outlook Error during the OS upgrade are:

• Damaged or Corrupt Outlook user profile
• The software is overwritten by some other program
• Outlook PST file corruption

The Mapi32.dll Outlook Error message is displayed in either of the following forms:

• Mapi32.dll is missing
• Cannot start Microsoft Office Outlook. Mapi32.dll is corrupt or the wrong version.
• Mapi32.dll was not found
• Mail is not installed

Further Information and Manual Repair

So, what if you experience this issue and how do you fix it? Well, first there is no need to panic as Microsoft has recognized this issue and provided adequate solutions to fix this problem in no time. However, to ensure the Mapi32.dll Outlook error is a quick fix, you must first understand the cause of the issue and the message displayed on the screen.

1. Let’s say the errors occur because your Outlook profile is corrupt. In this scenario, the best solution is to create a new Outlook profile. Regardless of whether you have Windows Vista or XP, to create your new Outlook profile, first, you will have to click on the Control Panel, then User Account, and then Mail. Once you click on the Mail tab, the mail set up dialog box will open. In this dialog box there will be a ‘Show Profiles’ tab, click and then click the Add tab that appears next. Now type the name for your new Outlook profile and then click ‘OK’. After that, add an email account to go with the profile.
2. If Mapi32.dll is missing or corrupt, you will have to run ‘Fixmapi.exe’ to resolve the problem. It is located in the System32 folder inside the Windows directory in Windows Explorer.

• Therefore, first start Windows Explorer and then locate the following folder on your computer: C: /Program Files/Common Files/System/Msmapi1033
• Now find Fixmapi.exe and double click it
• After that locate the Mapi32.dll file and rename it to MSmapi32.old and press enter.
• Restart your computer when finished.

A word of advice for computer users is to scan for viruses with an antivirus program or a registry cleaner regularly to prevent the Mapi32.dll Outlook error from occurring in the first place. Viruses often latch onto .dll files and corrupt them. It’s always best to have a forward-looking approach.

Error Code 0x8007007b – What is it?

This error code occurs when users fail to activate their Windows operating system. It is one of the more popular Windows error codes since it affects many versions of Windows including Windows 7, Windows 8.1, and Windows 10. Error code 0x8007007b has common symptoms which include the following:

• Inability to activate a Windows installation
• Message box highlighting error code 0x8007007b

Solution

Error Causes

Error code 0x8007007b in Windows 8.1 usually results due to one or more main clauses. Windows 8.1 users may experience this error due to the use of volume-licensed media. The error code may also arise if the activation wizard is unable to connect to Key Management Service (KMS) host computer or if corrupted system files are present on your computer.

Further Information and Manual Repair

Windows error codes such as Error code 0x8007007b can be a complicated issue, requiring the use of technical knowledge and skills. For this reason, we have listed instructions in the simplest of forms to enable even average users to successfully complete manual repair methods that will resolve error code 0x8007007b.

The same approach has been applied to all our error code solutions. See also Error Code 0x00000024 and Error Code 0x80004005.

Below are the two main methods for correcting this issue.

Method One: Use Multiple Activation Key (MAK) to Activate Windows

This method involves the use of a Multiple Activation Key (MAK) instead of the Key Management Service (KMS) to activate the Windows operating system you intend to use on your PC. This manual repair method requires the use of Command Prompt so ensure you follow the instructions provided carefully so as to avoid the risks of causing harm to your system.

• Step one: Select Windows log key + X.
• Step two: Click Command Prompt, then Admin
• Step three: Type in admin password if Command Prompt requests it
• Step four: Type slmgr -ipk followed by the MAK product key. Note that the product key should have 25 characters with dashes between them like this xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Attempt to activate your Windows installation once you’ve completed the exact instructions above. If you are unable to complete this process, consider getting help from a Windows repair technician or simply move to the next manual repair method listed below.

Method Two: Run System File Checker

System File Checker (SFC) enables Windows users to scan and repair errors or corruption on system files. Since such errors within your system files can cause error code 0x8007007b to occur, follow the steps below to fix this error code.

• Step One: Go to Start and type Command Prompt or CMD.
• Step Two: Run as Administrator
• Step Three: Type sfc /scannow with a space between “sfc” and “/scannow”.

The System File Checker tool will begin scanning your machine for corrupted or missing files in need of repair. If these files are found on your system, the tool will repair and replace them. Once this is done, restart your computer then check to see if you can now activate your Windows operating system.

Method Three: Use an Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 8 and other related issues when they do arise, download and install a powerful automated tool.

SMB which stands for “Server Message Block”, is a protocol used for file sharing. It provides the Read and Writes operating on network devices. Thus, it is why it is widely used when accessing a server-based in Linux. Its latest version is the SMB2 which follows after SMB1. The SMB2 contains more fixes to vulnerabilities that were found in SMB1. The predecessor was vulnerable since it served as a gateway to various modern ransomware which is why Microsoft disabled it by default starting with Windows 10 v1709. When you try to share a file, you will get the following error message:

“Microsoft Windows Network: You can’t connect to the file share because it is not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack. Your system requires SMB2 or higher.”

In this post, you will be guided on how to check if the SMB2.0 version can be installed on your Windows 10 computer. To get started, follow the steps below. Step 1: Tap the Win + X keys to open the Device Manager. Step 2: After that, click on the Windows PowerShell (Admin) option. Step 3: In the Windows PowerShell window, type the following command and hit Enter:

Get-SmbServerConfiguration | Select EnableSMB2Protocol

Note: After entering the command, you will see the following content on your screen which means that your Windows 10 computer is now capable of running the SMB2 protocol Now all that’s left for you to do is to enable the SMB 2 protocol on your Windows computer by enabling the SMB 1 protocol first and then upgrading it to SMB 2 afterward. Refer to the steps below for more details. Step 1: Tap the Win + I keys to open the Settings app. Step 2: Then type in “control panel” in the search area and click on Control Panel from the search results. Step 3: After opening Control Panel, click on Programs. From there, select the “Turn Windows features on or off” option under the larger menu of Programs and Features. Step 4: After that, Windows Features will appear on your screen. And from there, make sure that you select SMB 1.0/CIFS File Sharing Support and then click on OK. Step 5: Now let it install all the required files and then restart your computer to apply the changes made successfully. After your computer has restarted, the SMB 2 protocol should now be supported on your Windows 10 computer. Note: On the other hand, you can also enter the following command in the Windows PowerShell window. Just make sure you have admin rights to enable it.

Set-SmbServerConfiguration –EnableSMB2Protocol $true

The win32kfull.sys file is one of the kernel-mode device drivers in your Windows 10 operating system. In case you don’t know, there are two kinds of device drivers – the first ones are the normal drivers that communicate between your hardware and the operating system while the second ones are the kernel-mode drivers. The latter is necessary for booting your OS. And there are times when you encounter the win32kfull.sys error while booting your PC. Here’s the full context of the win32kfull.sys error:

“SYSTEM_SERVICE_EXCEPTION (win32kbase.sys) APC_INDEX_MIXMATCH PAGE_FAULT_IN_NONPAGED_AREA”

This error could be caused by corrupted or outdated drivers with incomplete files or it could be caused by some driver or software installed on your computer. To fix this error, here are some troubleshooting options you need to check out.

Option 1 – Try updating all the Drivers

As pointed out, the win32kfull.sys error can be due to outdated or corrupted drivers that are not compatible with your hardware. These drivers include but are not limited to display, network, sound, hard drive, and more. If you are not able to access the internet, you can just manually download the update using another PC. To update your drivers, here’s what you need to do:

• 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. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it. After that, you could also check if there’s a new update of the game you’re getting the issue of the black bar.

Option 2 – Identify and uninstall problematic programs by putting your PC in a Clean Boot State

One of the main causes of BSOD errors like win32kfull.sys is a problematic program that could clash with your existing operating system as well as computer architecture. There are tons of programs that are either incompatible or conflict with the existing drivers or software in your system. To identify such programs, you need to put your PC in a Clean Boot state. How? Follow these steps:

• 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” checkbox 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” checkbox.
• 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.)

After putting your PC in a Clean Boot State, try creating a system restore point and see if the problem still occurs. Clean Boot troubleshooting is designed to help you isolate the problem. For you to execute a clean boot troubleshooting, you must do a couple of actions (the steps are given above) and then restart your PC after every action. You might have to disable one third-party app after the other to really isolate the issue. And once you’ve narrowed down the problem, you can either disable the third-party app that’s causing the problem or remove it. Note that you must switch your PC back into the Normal Startup mode after you’re done troubleshooting the problem. Here’s how you can do it:

• From the “Start” menu, go to System Configuration.
• After that, switch to the General tab and click the option for “Normal Startup”.
• Next, go to the Services tab and clear the checkbox for “Hide all Microsoft services”.
• Then find and click “Enable all” and if prompted, you have to confirm.
• Afterward, go to the Task Manager and enable all the Startup programs and confirm the action.
• Restart your PC when prompted.

Once you have identified the program causing the problem, uninstall it right away from your Control Panel.

Option 3 – Perform an SFC scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the win32kfull.sys error. 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 to 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.

Windows defender error 0x800700AA, service can not be started comes when the user is trying to run Windows defender scan on their system. This kind of behavior happens for two reasons mostly, third-party application conflict or corrupted system files. In this article, we will tackle both scenarios and provide you with solutions in both cases.

Third-party application conflict

In this rare scenario when Windows defender can not start scan due to conflict with installed service or application in the system solution is quite simple. Restart your PC into safe mode and run the scan from there. In a safe mode environment, minimum drivers and services are only loaded eliminating any conflicts that might occur when everything is booted. If Windows defender can not run the scan in safe mode and you get the same 0x800700AA error then you can eliminate application conflict as a reason and move to the next solution which will tackle corrupted system files. If you, however, managed to run a scan then you have a rare third-party application conflict, you can boot normally into windows and try to eliminate one by one to see which one is causing the issue. The safest bet would be to start with security software because most of the time that is what causes conflicts in running services and applications.

Corrupted system files

If the previous solution has not provided you with results then you have system file corruption that needs to be fixed. Move from one solution to another as presented below:

1. Run SFC scan

   SFC scan is a built-in Windows tool for solving corrupted system files issues, it is fully automated and does not require from the user any kind of knowledge or information. To run it and scan the system do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) In command prompt type SFC /SCANNOW and press ENTER Wait for the process to finish, do not interrupt it and once it is done, restart your computer

2. Run DISM scan

   DISM scan is similar to SFC scan but it tackles different types of system file corruption and it is recommended to run it also after SFC has been completed. Please note that for DISM scan to be successful you will need a stable internet connection since DISM will replace corrupted files with new ones downloaded from Microsoft. To run it do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) inside command prompt type: exe /online /cleanup-image /scanhealth followed by ENTER, then type: Dism.exe /online /cleanup-image /restorehealth also followed with ENTER. Leave scan to finish and reboot your PC

A few days ago we celebrated fixing of months-long PrintNightmare vulnerability by Microsoft, sadly a new bug and issue have been found. Firstly discovered Microsoft stated:

A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

A few days ago, Microsoft officially released a patch that was supposed to finally fix it. As you might recall this vulnerability was present for quite some time, Microsoft's solution after a long struggle was to elevate certain privileges to administrator account only and remove user accounts from managing printers. It complicated things a little bit but it was stated payoff was worth it. The new issue now is that on a system that already had accounts created and set, old accounts still can hijack the system, patch issues address only accounts that are created after the fix is administrated, old ones can still do whatever they want. Once again of course Microsoft has stated that until it is again resolved you should again disable the Print Spooler service as a temporary workaround.

The “Unknown Hard” error that keeps on appearing in Windows 10 can put users in an unpleasant situation. This kind of error leads to the freezing of the taskbar, blackening of the screen, and sudden disappearance of the icons on the Desktop. And each time you try to open Windows, the system will only give you an error message saying that it’s a critical error and some applications like Start and Cortana won’t work. Upon analysis, it seems that the “sihost.exe” is not responding and that it is the one that’s causing the c000021a Unknown Hard error to pop up. Sihost.exe files represent the Shell Infrastructure Host which is an essential component in the Windows operating system. The Windows Shell Infrastructure Host is primarily responsible for handling some graphical elements of the operating system interface such as the Start menu and the taskbar transparency. And so if the Shell Infrastructure or Sihost.exe has stopped, has been removed, or corrupted, you will most likely have issues with the overall functionality of the Windows operating system and you’ll get the Unknown Hard error In addition, the ctfmom.exe Unknown Hard error may also occur due to incompatible drivers installed on your PC. Ctfmom is a process that identifies inputs such as handwriting, languages, and many more. It’s the one that controls the functions of background behavior. To resolve this issue, you need to first try to identify which application is the one that’s running the sihost.exe file. And if needed, you need to either update or reinstall or completely uninstall the problematic application.

Option 1 – Try to run the System File Checker

The SFC Scan or System File Checker, us a built-in utility in Microsoft Windows that can be found in the C:\Windows\System32 folder. This tool allows users to scan and restore any corrupted system files in Windows that might be causing the Unknown Hard error to appear. Before you use this tool, make sure to find out whether the sihost.exe on your computer is a Trojan that you have to remove or if it’s a file that belongs to a trusted Windows application. Once you have that sorted out, follow the steps 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 2 – Try to use System Restore

You can also try using System Restore. This is one of the ways you can use it to back up your PC. Since restore points are created automatically each week by System Restore, you can use System Restore to restore your computer back to an earlier good point in time.

Option 3 – Try to troubleshoot the error in a Clean Boot State

Putting your PC in a Clean Boot state can help you diagnose and troubleshoot the issues in your system. During this state, you can start the system with a minimum number of drivers and startup programs that will surely help you in isolating the root cause of the Unknown Hard Error.

• 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” checkbox 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” checkbox.
• 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.)

After putting your PC in a Clean Boot State, try creating a system restore point and see if the problem still occurs. Clean Boot troubleshooting is designed to help you isolate the problem. For you to execute a clean boot troubleshooting, you must do a couple of actions (the steps are given above) and then restart your PC after every action. You might have to disable one third-party app after the other to really isolate the issue. And once you’ve narrowed down the problem, you can either disable the third-party app that’s causing the problem or remove it. Note that you must switch your PC back into the Normal Startup mode after you’re done troubleshooting the problem. Here’s how you can do it:

• From the “Start” menu, go to System Configuration.
• After that, switch to the General tab and click the option for “Normal Startup”.
• Next, go to the Services tab and clear the checkbox for “Hide all Microsoft services”.
• Then find and click “Enable all” and if prompted, you have to confirm.
• Afterward, go to the Task Manager and enable all the Startup programs and confirm the action.
• Restart your PC when prompted.