Logo

Fix Microsoft Store error 0x80072F30

If you got the Microsoft Store error code 0x80072F30 while trying to open Microsoft Store, then it indicates that the Store fails to connect to the internet or is not able to launch successfully for some reason. It could be that the Windows Update Service has stopped or the Windows Store cache might be corrupted or it could just be due to a poor internet connection. Whichever the cause is, you have to fix this error so that you can use Microsoft Store again and you won’t be getting the following error message every time you open the app:

“Check your connection, Microsoft Store needs to be online, It looks like you are not, error code 0x80072f30.”

The error code 0x80072F30 is related to the Windows Store which prevents it from opening properly. To resolve this problem, you can try fixing the problem with the help of the options given below. Follow each one of them carefully.

Option 1 – Check your internet connection

The first and most obvious thing you can do is to check your internet connection. This may only be a basic tip but it sure works like a charm in most cases. And if you have another internet connection available, you can also try connecting to that and see if you can pull up Microsoft Store or not.

1] Change your internet connection:

A basic tip, but sometimes works like a charm. You may want to check if your internet connection has an issue, or you can also try opening a website and see if you can open it and if possible try connecting to a different internet connection and see if the Microsoft Store opens for you. We also suggest you try changing your DNS and see if it helps.

Option 2 – Check the date and time as well as the time zone of your PC

A lot of services and apps rely on the Date, Time, and Time Zone of your PC which is why if they are not configured correctly, a request from the client machine will be rejected from the server and the same thing happens with the Microsoft Store.

  • First, go to Settings > Time and Language.
  • From there, check if it is set to Automatic or not – if it is, switch the toggle button off to set the Time and Time zone manually.
  • Then select the right time zone manually.
  • On the other hand, if the Time and Time zone is set manually, you have to switch the toggle button on to set Time and Time zone automatically.
  • Restart your PC and afterward try opening Microsoft Store again and check if the problem’s fixed or not.

Option 3 – Run the Network Adapter Troubleshooter

Since Windows 10 is packed with various troubleshooters – one of which is the Network Adapter Troubleshooter – you can use it to troubleshoot the problem. To use it, follow these steps:

  • Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
  • Next, scroll down and select the “Network Adapter” option from the right pane.
  • Then click on the Run Troubleshooter” button.
  • After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.

Option 4 – Try to reset the Microsoft Store cache

Just like browsers, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

  • Right-click on the start button and click on Command Prompt (administrator).
  • Next, type in the command, “exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
  • Now restart your PC and afterward, try opening Microsoft Store again.

Option 5 – Check the Windows Update Service status

You might also want to check the status of the Windows Update Service since the proper functioning of this app depends on the Windows Update Service. It could be that there is some issue with the service which is why you’re getting the error code 0x80072F30 while trying to open Microsoft Store.

  • Tap the Win + R keys to open the Run dialog box.
  • Then type “services.msc” in the field and hit Enter to open Services.
  • Next, look for Windows Update Service from the list of available services in Windows.
  • Once you see it, check if its status is STOP or Pause and then change the status to Automatic.

Do You Need Help with Your Device?

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

Share this article:

You might also like

How to Fix Propsys.dll Error
Isn’t it annoying when you get an error message pop up stating ‘Cannot find propsys.dll” or “propsys.dll not found” when you start your computer or open a particular program? The propsys.dll file is crucial to the Windows operating system. This file is located in one of the following locations: "C:\Windows", C:\Program Files, C:\WINDOWS\system32, or C:\Program Files\Common Files". And the propsys.dll error indicates that the propsys digital library file is damaged and corrupt. The propsys.dll error may lead to a very unstable operating system. It may also hamper your ability to access many programs on your computer, lead to program and system crash and slow down the system’s performance. Therefore, to avoid these system threats, it is advisable to fix the error immediately.

Solution

Restoro box imageError Causes

The common causes of propsys.dll file error are:
  • Registry problem
  • The propsys.dll file is damaged due to a virus or spyware
  • Improper software removal
  • Hardware Failure
The propsys.dll error message is displayed in either of the following forms:
  • Propsys.dll not found
  • Cannot find [Path]propsys.dll
  • This application failed to start because propsys.dll was not found. Reinstalling the application may fix this problem
  • The propsys.dll file is missing

Further Information and Manual Repair

There are many ways to fix the propsys.dll error. However, for optimum results from the fix, you must first identify the cause of the error and then choose the solution accordingly.
  • Recommended Solution for Registry Issue
If you use your system daily the resulting wasted/invalid/junk entries may dilate the registries. This can result in registry malfunctioning which may result in a propsys.dll error on your screen. When this happens, it is advisable to use a registry cleaner to fix the problem. Registry cleaner helps clean up the junk entries and repairing the corrupted registries. For this, you will first have to download a registry cleaner repair tool. Download and install the software on your computer. After downloading it, click the start scan button to run. This helps scan and diagnose system errors on your computer in seconds. Once the scanning is complete, click on the fix button to repair the registry problem.
  • Recommended Solution for File Damage and Corruption
Use the ‘System Restore’ option to restore corrupt and damaged files.  The ‘System Restore’ function will help you get a fresh copy back and simultaneously help fix the error. Here’s how to use and access the ‘System Restore’ function on your computer: Simply go to the start menu and in the search box type restore. Once you type, it will show you the system restore option. Now select ‘choose a different restore point’. After this, you will be presented with a list of restore points. Choose a point that you believe happened before the propsys.dll error. Confirm your selection and restart. Another alternative solution for file damage is to run a virus scan of your entire system; the damage could be related to a virus or malware infection.
  • Recommended Solution for Hardware Failure
If a propsys.dll error occurs due to hardware failure, then it is advisable to update the drivers for hardware devices that you think are related to propsys.dll. For example, if you receive the propsys.dll error when you play a 3D video game, then try updating the driver for your video card.
Read More
Windows 11 Insider Preview Build 22000.71
Microsoft just released Windows 11 Insider build 22000.71. Let’s dive in and see what it brings with you.

windows insider 2000Changes 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.
Read More
How to Fix Error Code 0xC004C003 When Installing Windows 10

What is Error Code 0xC004C003?

Error code 0xC004C003 has to do with activating Windows 10 after a clean install. This problem has been a frequent nuisance to users trying to update from Windows 7 or 8.1 following the invite path they got from Microsoft.

Solution

Restoro box imageError Causes

There are several problems that may have caused error code 0xC004C003. The most common of them are:
  • The product key entered was invalid, and cannot be used to activate the new OS.
  • The user followed the proper installation procedure, but the Windows update servers were too busy to handle the activation at that moment.
  • The free upgrade invitation was followed but after the reinstallation, the copy of Windows 10 was still not activated.
  • The user tried to perform a full clean install of Windows 10 instead of upgrading from Windows to Windows 10

Further Information and Manual Repair

A lot of solving error code 0xC004C003 has to do with the method in which the user has tried to update the system. If one decided to try and update the program before being invited to do so by the update manager, he must wait. Unfortunately, if one chooses to do it on his own and download a clean install, he was never given a product code to authenticate the process. There are two options to address error code 0xC004C003 — either restore to the previous Windows Operating System or call Microsoft (or visit their Website) and purchase a product key. The Windows update servers are very busy. There are lots of Microsoft users around the world, and the servers are doing their best to get to each and every one of the users as fast as possible, but they can only move at a certain speed. Your best bet is to sit back and wait a while. But what if you were invited, and properly downloaded Windows 10, then decided to do a clean install? It is advised that one do not try to enter Windows 7 or 8.1 serial code as this will not work. However, unlike the problem above, these users will NOT need to purchase a product key. According to Microsoft Support Staff, the installation servers are also very jammed because of the high numbers of installations going on right now. No matter what posts you may read, the key IS genuine, and it is NOT blocked, broken, or invalid. To check if Windows has been properly activated, open the Command Window. Make sure you are logged into an administrator profile; otherwise this check will not work. Type in “slmgr.vbs/ato” and click Enter and then wait. While waiting, the command will check on the status of the activation. Windows Script Host will open and show whether or not it is activated. A lot of users have reported that the activation did not work for the first few times. However they later reported after some more attempts, no issue was found in the way the operating system updated and that the activation process went smoothly. This is most likely due to the overload on the Windows Update servers, so bear with Microsoft. Users have reported that when trying to correct error code 0xC004C003, they have followed the upgrade path and then been told by Microsoft that the key was invalid and they had to purchase a new one. If the upgrade path provided by Windows 7 and Windows 8.1 is correctly followed then there is nothing to worry about Just wait a while and try it again. If there are prolonged issues, speak with a technician by visiting the Microsoft website and contacting the help center by calling the number provided. Give them all relevant information and they will be sure to help accordingly. The best solution to fix error code 0xC004C003 is to wait. In essence, the user will be waiting to reenter the same product key. According to Microsoft, and many user posts found online, it is recommended to wait a while and then try to activate again. This seemed to be an answer to most users' problems, and seem to work just fine. If the problem persists, take it to a windows repair technician to have it sorted out. If that does not work, use a powerful automated tool to fix the problem.
Read More
Fix Windows Cannot Find a System Image
If you have encountered the “Windows Cannot Find a System Image on This Computer” error while you are trying to restore a system image, then read on as this post will guide you in resolving this problem. A system image is basically a backup of your whole data in the system. For instance, it can be the backup data of your hard disk or the whole hard disk itself, or one of the volumes. This is really useful in some cases like when you are not able to get back into your system for some reason or when your system has been corrupted. In such cases, you can utilize this feature and get going safe and sound. However, not all things go the way as expected like when you make a system image of a drive for instance, or use that backup to restore data and you suddenly encounter the “Windows Cannot Find a System Image on This Computer” error. This kind of error occurs due to a number of reasons but worry not for your data is safe and you can fix this error easily. This error is most likely triggered by changing the name of the “WindowsImageBackup” folder. Renaming this folder will certainly be an issue since it is the one that stores all your data. Aside from renaming the WindowsImageBackup folder, renaming the sub-folders can also cause this error which means that renaming the sub-folders of the WindowsImageBackup folder can trigger the error. To fix this error, here are some suggestions that might help:

Option 1 – Try putting the WindowsImageBackup folder in the Root directory

Windows will have issues finding the WindowsImageBackup folder if it isn’t in the root directory of the drive so if it is not there, the “Windows Cannot Find a System Image on This Computer” error will pop up. When a folder is in a root directory, it means that it shouldn’t be stored within a folder but in the main directory instead.  Thus, you need to put the WindowsImageBackup folder in the root directory to fix the error.

Option 2 – Don’t add any sub-folders in the WindowsImageBackup folder

Another cause of the error is when you add sub-folders in the WindowsImage Backup folder. Adding any sub-folders in this folder will only trigger the error so you should leave the folder as it is and you must not make any modifications to it. So if you have added sub-folders in it, make sure to remove them right away.

Option 3 – Make sure that there is one system image per USB drive

The error can also appear if you’ve stored multiple images inside a single USB drive as it could confuse Windows and will trigger the “Windows Cannot Find a System Image on This Computer” error. Note that storing system images of different volumes of your hard disk in a single USB will prevent you from restoring your data.

Option 4 – Try renaming the System Image folder

If you’ve just changed the name of the System Image folder after you store it on a USB stick or other external device, then it’s no wonder why you’re getting the “Windows Cannot Find a System Image on This Computer” error. Windows search for the default name, “WindowsImage Backup” folder when restoring your data so if it is not able to find it, it throws up this error instead. To fix the error, you need to change the folder back to its default name which is “WindowsImageBackup”.

Option 5 – Check the WindowsImageBackup sub-folders

As mentioned earlier, renaming sub-folders in the WindowsImageBackup folder can trigger the error so if you have renamed sub-folders in this folder, you need to change them back to their default names so that you can restore your data peacefully.
Read More
How to Fix Can’t start your Camera, 0xa00f429f
If you are using the Camera app on your Windows 10 computer but encountered an error code 0xa00f429f with an error message that says, “Can’t start your camera”, read on as this post will guide you in fixing this problem. This kind of error in the Camera app could be due to a recent update gone wrong or it could also be due to a corrupted driver. If you are certain that the camera is connected and is properly installed, you can try to check for updated drivers. The error code signifies that the drivers have to be updated. However, that isn’t always the case sometimes as the problem could also have something to do with corruption in the driver. The effective ways to troubleshoot this problem would be trying to reinstall or reset the Windows Camera app, or update, rollback or uninstall some device drivers as well as use the Registry Editor. Before you proceed with the instructions provided below, make sure that you have admin privileges and don’t forget to create a System Restore point.

Option 1 – Try to reset or reinstall the Windows Camera app

As pointed out earlier, you can also reset the Camera app to fix the error. To do so, follow the steps below.
  • The first thing you have to do is go to the My Pictures folder under the C: drive of the File Explorer and then delete the Camera Roll folder.
  • Once you’re done, right-click on an empty area on your screen and create a new folder and name it “Camera Roll”.
  • Then from the Start menu open the Settings app and select System.
  • From there, navigate to the Apps and features section.
  • Now go to Camera and click on the Advanced Options and click the Reset button.

Option 2 – Try to reinstall the Camera app

If resetting the Camera app didn’t help, you might want to reinstall it by following these steps:
  • Tap the Win + X keys and select the “Windows PowerShell (Admin)” option from the menu to open Windows PowerShell as admin.
  • Next, type this command to uninstall the Camera app: Get-AppxPackage *camera* | Remove-AppxPackage
  • Once done, exit the Windows PowerShell and restart your computer and then try to install the latest version of the Camera app from Microsoft Store.

Option 3 – Try to rollback, update or disable drivers

The next thing you can do to fix the error code 0xa00f429f in the Camera app is to roll back, or update, or disable 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.
  • After opening the Device Manager, look for the device drivers which have a yellow exclamation mark.
  • Then right-click on each one of them. If you haven’t updated this driver in a while, select the “Update Driver” option. On the other hand, if you’ve just updated this driver, then select the Uninstall Device option.
  • Next, follow the screen option to update or uninstall it.
  • Finally, restart your computer. It will just reinstall the device drivers automatically if you have chosen to uninstall them.
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.

Option 4 – Try to use the Registry Editor

  • Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and then hit Enter to open the Registry Editor.
  • Next, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREWOW6432NodeMicrosoftWindows Media FoundationPlatform
  • From there, right-click on any empty space on the right side part of the window and select New > DWORD (32-bit) Value.
  • Then name it as “EnableFrameServerMode” and double click on it.
  • Now set its value data to “0” and its base value as Hexadecimal and then click on OK.
  • After that, restart your computer and see if it helped in fixing the problem or not.
Read More
How to Fix DCOM Error 1084 on Windows
Distributed Component Object Model or DCOM is a module on Windows computers that allows computers to run programs over a network to another computer. It is a software component from Microsoft that allows COM objects to communicate with each other while that program is remotely running over the network. The COM Model is another extension of the DCOM model which both work together in order for the intended task to be executed. To make this module work, there are three components needed such as the Class Identifier or CLSID, the Programmatic Identifier or PROGID, and the Application Identifier or APPID. However, DCOM does not always work as expected as it could still encounter some errors. One of them is error 1084. Because of this error, the execution of programs in a remote computer on the network would be interrupted. So if you encounter the DCOM error 1084 when you try to start a service like running the DISM tool or in other scenarios on your Windows 10 computer, then this post could help you. Refer to the instructions given below to start troubleshooting the problem.

Option 1 – Try checking the status of DCOMLAUNCH Service or DCOM Server Process Launcher and its 3 dependencies

The DCOM Server Process Launcher service launches both COM and DCOM servers in response to object activation requests. This is why if this service is stopped or disabled, the programs that are using COM and DCOM won’t properly function. So you need to make sure that the DCOMLAUNCH service is running.
  • In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
  • Next, check the following services:
    • DCOM Service Process Launcher
    • Background Tasks Infrastructure Service
    • Local Session Manager
    • Remote Procedure Call (RPC)
  • Then right-click on each one of the services and click on their Properties.
  • After that, select Automatic from the drop-down menu of Startup Type and make sure that all the aforementioned services are Running.
  • Now click OK for each one of the services.

Option 2 – Troubleshoot the problem in a Clean Boot State

There are instances that some conflicting programs installed in your computer might be the one that’s causing DCOM error 1084. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.
  • Log onto your PC as an administrator.
  • Type in MSConfig in the Start Search to open the System Configuration utility.
  • From there, go to the General tab and click “Selective startup”.
  • Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
  • Next, click the Services tab and select the “Hide All Microsoft Services” check box.
  • Click Disable all.
  • Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
  • From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Option 3 – Try to use the DISM tool

You might want to repair potentially corrupted files in your system as having them could also trigger the DCOM error 1084. To repair these corrupted system files, you can run the DISM commands:
  • Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
  • After that, input each one of the commands listed below sequentially to execute them:
    • Dism /Online /Cleanup-Image /CheckHealth
    • Dism /Online /Cleanup-Image /ScanHealth
    • Dism /Online /Cleanup-Image /RestoreHealth
  • Once you’ve executed the commands given above, restart your computer and check if the DCOM error is now fixed.

Option 4 – Reset your computer

  • 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
Mapped network drives are not working
When you have to connect to a drive that’s on a different computer or on external storage, that’s where the mapped network drives come in. Mapped network drives make accessing files a lot easier. However, there are times when it won’t work for some reason. Windows will notify you about the unavailability of mapped network drives in several ways. For one, Windows might display a red X on the network drives or it could be that its status will be unavailable when you try to use it from the Command Prompt or via a notification. It is recommended that you run a few scripts when you log in to your PC as it may so happen that the network drive takes more than usual to connect. Before you start troubleshooting the problem using the given options below, keep in mind that some workouts might only work under certain scenarios. You might need some network access at logon or you might need access to the Group Policy settings. So you need to choose what you prefer more. You can try the given workarounds below if the mapped network drives are not showing or connecting or working on your Windows 10 computer. These workarounds use scripts to make sure that you are connected to them as soon as you start to use your PC. As mentioned, before you can troubleshoot, you need to create scripts first. There are two scripts here namely MapDrives.ps1 which is executed by the second script named MapDrives.cmd and is done at a regular and non-elevated Command Prompt. Follow the steps below to get started.
  • You have to create a script file named “MapDrives.cmd” first and then save it on a place where the files are safe. To do that, open a text editor like Notepad and then copy and paste the following script:
PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%StartupLog.txt" 2>&1 PowerShell -File "%SystemDrive%ScriptsMapDrives.ps1" >> "%TEMP%StartupLog.txt" 2>&1
  • After that, save the file and name it “MapDrives.cmd”.
  • Next, create a script file named “MapDrives.ps1” and then copy and paste the following content. Just make sure to save both scripts in the same folder.
$i=3 while($True){     $error.clear()     $MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath     foreach( $MappedDrive in $MappedDrives)     {         try {             New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True         } catch {             Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath"         }     }     $i = $i - 1     if($error.Count -eq 0 -Or $i -eq 0) {break}     Start-Sleep -Seconds 30 } Note: Now that you’ve created the script files, it’s time for you to proceed to the options given below.

Option 1 – Try creating a startup item

Note that this option only works on devices that have network access at login. So if it’s not there, the script will fail to reconnect the network drivers automatically. To create a startup item, here’s what you have to do:
  • Open the Startup folder located at %ProgramData%MicrosoftWindowsStart MenuProgramsStartUp.
  • From there, copy and paste the MapDrives.cmd.
  • After that, open the Scripts folder located at %SystemDrive%Scripts copy-paste MapDrives.ps1 and then copy and paste MapDrives.ps1 in there.
Note: After you complete the steps above, a log file named “StartupLog.txt” will be created in the %TEMP% folder. Now all that’s left for you to do is to log out of your computer and then log back in. This will ensure that the mapped drives are open.

Option 2 – Create a scheduled task

It is possible to create a scheduled task that runs as soon as you log in to your computer. To create a scheduled task, follow the steps below.
  • You have to copy the MapDrives.ps1 script file to the scripts folder of Windows located at %SystemDrive%Scripts.
  • After that, open the Task Scheduler and select Action > Create Task.
  • Next, type a name and description of the task in the General tab.
  • Then click on the Change User or Group button and select a local user group and click OK.
  • Now check the box labeled “Run with highest privileges” and switch to the Triggers tab.
  • From there, create a new trigger with the “At Logon” option in the Begin the task drop-down menu and then click OK.
  • After that, switch to the Actions tab and create a new action then choose to Start a program.
  • Next, type “Powershell.exe” in the Program/Script field, and in the Add arguments (optional) field, type the following:
-windowsstyle hidden -command .MapDrives.ps1 >> %TEMP%StartupLog.txt 2>&1
  • And in the Start in the (optional) field, type “%SystemDrive%Scripts” as the location of the script file.
  • Now under the Conditions tab, select the “Start only if the following network connection is available” option and then select Any connection and click OK.
  • Restart your computer or log off from your account and then log back in so that the task will be executed.

Option 3 – Use the Group Policy settings

You need this option if the mapped network drives are defined via Group Policy settings. You have to update the action of the drive maps to Replace. As a result, it will delete the existing mapped drive and create the mapping on each logon again. However, any settings on the mapped drive that are changed from the Group Policy settings will be gone on each logon. So if the changes don’t work, you need to run the gpupdate command together with the /force parameter in order to refresh the Group Policy setting quickly.
Read More
Malware Guide: How to Remove Webguard

What is Webguard?

Developed by Interesting Solutions, Webguard is a tool supposedly used for tracking those online who’ve developed a habit of tracking you. The application would provide logical analysis into a user’s website history, providing insight on what websites you’ve visited and also how persons are able to track your every move while browsing. While Webguard is unable to dispose of who specifically is tracking your computer usage, they’re able to determine what computer installed tracking codes or cookies on your computer system. In this case, it’s then left up to the user’s discretion to determine who they want to allow or block from tracking their online use.  Overall, this application allows the user some measure of freedom and control over their online experience. Like any other application, however, which has landed themselves a spot on Virus Total, Web guard has hidden agendas. At a distance, Webguard installs a service for Windows but later distributes advertisements. Technical details about Webguard include:
Product Version: 1.0.0.0 Original File Name: crss.exe Entry Point:  0x000C5AAE

Assessment of Webguard Potentially Unwanted Program

While Webguard claims to track your computer usage, information reported by the application isn’t sufficient for the common computer user. This brings us back to the ulterior motive or principal objective of developing Webguard – to advertise and generate revenue from clicks made by users on Ads displayed on Internet Browsers – namely Chrome, Internet Explorer and Firefox. Why should a computer user remove Webguard? Simply, it compromises one's Internet privacy and security and it keeps abreast of your Internet history. If you’re online for an extended period, you’ll see what Webguard does. While the publishers behind the application did not alert users to the use of web beacons, cookies for tracking, and other related tracking technology, that’s not why Webguard is considered unwanted. The program is potentially unwanted because of the unpredictable advertisements it displays. Not all sites are trusted and so it’s difficult to determine, in some cases, what websites are legit for business.

Remove Webguard with Spyhunter

In most cases, at least from what I’ve seen, Webguard is installed as a single application. After it was installed for this assessment, it could be found in ‘All Programs”. This meant that one could manually delete the application from their computer system (see manual steps below). However, is that really sufficient to completely rid your PC of Webguard’s blueprints? While you might opt to remove Webguard manually – maybe because it’s more economical – an automated process is able to completely eradicate hidden threats from Webguard. In comparison to manually removing Webguard, Spyhunter penetrates your computer system for all infections. In most cases, nasty threats are unable to be removed manually. Additionally, Spyhunter not only removes installed threats, but it detects incoming ones – hence, acting as a preventative tool. Furthermore, Spyhunter detects cookies placed on your computer by Webguard. These are all undetectable threats and so an automated tool, as Spyhunter, should be used to remove Spyhunter effectively from your computer.

Manual Steps for Removal of Webguard

I found this removal pretty simple. Depending on your Operating System, there will be slight discrepancies in the manual removal steps. Using the Windows 8 (8.1) OS on your computer:
  • Step 1: Locate the CONTROL PANEL on your computer using the SEARCH option.
  • Step 2: Once the search box appears , input 'CONTROL PANEL'.
  • Step 3: The Control Panel option will then appear. From the menu, choose the "Programs" option.
  • Step 4: Another menu will appear. Select "All Programs and Features".
  • Step 5: From the 'Programs list', search for the Webguard application.
  • Step 6: Right-click on Webguard when it's found.
  • Step 7:  Choose the "Uninstall" option.
  • Step 8:  Follow the uninstall wizard instructions until the Webguard application is fully removed.
To completely remove Bandoo from your computer, click here to download and install Spyhunter
Read More
How to Fix Unknown Hard Error in Windows 10
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.
Read More
How to remove weather widget from W11
The latest Windows 11 update has brought with it not so popular widget from Windows 10, the weather widget that will reside into the taskbar and constantly show stuff like temperature, weather conditions, etc. The weather widget is not a bad thing but most users found it a little annoying and turned it off in Windows 10. If you wonder how can you do the same but this time inside Windows 11 please keep reading. weather widgetThe first step is to right-click  anywhere on the taskbar (in empty space) and choose Taskbar settings Once the taskbar settings are opened, find Widgets and click on the switch on the far right to turn it off, immediately no more information will be shown on the taskbar and it will be free again. And that is all there is to it.
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