Fix Slow download speeds for MS Store

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

Changes and features

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

Fixes

Taskbar:

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

Settings:

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

File Explorer:

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

Search:

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

Widgets:

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

Other:

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

Known issues in Windows 11 repaired

Start:

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

Taskbar:

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

Settings:

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

File Explorer:

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

Search:

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

Widgets:

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

Store:

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

Windows Security:

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

Localization:

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

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

If you encounter the NMI_HARDWARE_FAILURE Blue Screen error while using your Windows 10 computer, then read on as this post will guide you in resolving this kind of Blue Screen of Death error. NMI HARDWARE FAILURE or “Non-Maskable Interrupt” Blue Screen error occurs when there is some hardware malfunction in your computer. When you encounter this Blue Screen error, you may get a stop code of 0x00000080 which can randomly occur while you use your computer. However, a lot of users reported encountering this error while they were trying to update or install their Graphics Card drivers. The stop code that you may get for this BSOD error is 0x00000080. The error can occur randomly during your usage of the computer – but a large number of users have reported this error while they are updating or installing their Graphics Card drivers. In this post, we will be covering all the possible fixes for this error. NMI_HARDWARE_FAILURE error on Windows The NMI_HARDWARE_FAILURE bug check has a value of 0x00000080. This bug check indicates that a hardware malfunction has occurred. There are various hardware malfunctions that can cause this kind of Blue Screen error. However, pinpointing the exact cause is quite difficult. Worry no more for the following fixes provided below can help you resolve the NMI_HARDWARE_FAILURE Blue Screen error no matter what the cause of the problem is.

Option 1 – Try removing hardware or drivers that you’ve installed recently

If you have recently installed some hardware or drivers, you might want to disable or remove them since external devices are proven to be one of the factors that trigger Blue Screen errors like NMI_HARDWARE_FAILURE. All you have to do is physically disconnect any external devices that are connected to your computer and then check if it fixes the BSOD error or not.

Option 2 – Try to rollback, update, or disable the Graphics card drivers

Since the NMI_HARDWARE_FAILURE Blue Screen error has something to do with Graphics card drivers, you can either roll back, update or disable them depending on your preference in order to resolve the error.

• 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 the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters 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.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 3 – Make sure that all memory modules have the same type

This third option is quite technical and tricky. If you often use multiple physical RAMS on your Windows 10 computer, then you have to check first if they are of the same frequency. After that, the first thing you should verify is if the chip is properly compatible or not. And if the sockets are attached using some kind of adapter or non-recommended device, it could cause some issues while giving a performance hit to your computer.  If you were able to find such a setup, you have to undo it or install the proper and recommended as well as compatible hardware.

Option 4 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like the NMI_HARDWARE_FAILURE 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.

Did you know you can use emoji in file names inside Windows 10? It is no secret that emojis are basically everywhere and Microsoft has seen this and integrated them into Windows itself, so you can name files using emojis or combine them with text. Placing emojis in file names or in the text is extremely easy, all you have to do is press ⊞ WINDOWS + . and the emoji dialog will open from where you can find which emoji you would like to use. And that's it, you just used emoji for the file naming.

!!!NOTE!!!

In theory, some applications may not like these emojis if they don’t support Unicode characters. However, modern applications are designed to work with a broad set of languages that should properly support emojis. For example, the classic Windows Command Prompt can’t see emoji characters in file names properly, but both PowerShell and Microsoft’s new Windows Terminal can display them properly. If you do run into a problem, you can always open File Explorer and rename the affected files and folders to remove the emoji characters. You can then use those files in applications that don’t properly support emoji file names.

As you know, each time you log out of your Windows 10 computer, it will take you to the login screen where you can switch users or log back in. But there are instances where Windows 10 remains stuck on the signing out screen, along with a blue spinning circle and all you can see is the process of your computer signing out, however, it does not progress and only gets stuck there. Thus, in this post, you will be guided on how you can resolve such an issue on your Windows 10 computer. So if you are one of the users who experience the same problem, there are several fixes you can check out if your computer is stuck on the signing out screen with a blue spinning circle. You can try to force shutdown your computer or troubleshoot the problem in a Clean Boot State. You could also try to check the status of the User Profile Service or repair User Profile, as well as run System Restore. For more details, refer to each one of the suggestions provided below. But before you troubleshoot the problem, make sure that you are logged in to your computer as an administrator.

Option 1 – Try to force shutdown your computer

The first thing you can do is to force reboot your computer as this simple fix could help in fixing the problem. This option is quite simple, just make sure that before you do it, you have to save all your work.

• First, turn on your computer and press and hold the power button for at least 30 seconds. You might notice the screen flashing or making any changes, just ignore it.
• After that, plug out and plug in your computer and automatically turn it on.
• Once done, check if the issue is now fixed or not.

Option 2 – Put your computer in a Clean Boot State

It is possible that some third-party application is causing your computer to get stuck in the signing out screen. So you can try putting your computer in a Clean Boot State and see if it fixes the problem.

• 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.)
• Once your computer is in a Clean Boot State, you should now be able to sign out or sign in without any problem.

Option 3 – Try checking the status of the User Profile Service

If forcing your computer to shut down or putting your computer in a Clean Boot State didn’t fix the problem, you can try to check the status of the User Profile Service since it is the one responsible for loading and unloading user profiles. Thus, if this service is disabled or stopped, you will no longer be able to sign out or sign in successfully.

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Services Manager.
• From there, look for the User Profile Service and make sure that its Startup Type is set to Automatic and that its status is “Started”.
• Once done, exit the Services Manager and see if the issue is resolved.

Option 4 – Try to repair your corrupted profile via Registry

In this second option, you can try to repair the corrupted profile using the Registry but before you proceed, make sure to create a System Restore Point and then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “regedit” in the field and hit Enter or click OK to open the Registry Editor.
• Next, go to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
• Once you’ve opened the registry key, you should see a list of all the user profiles on your computer. Now click on each S-1-5 folder and look for the “ProfileImagePath” entry and double click on it to check which user account it is related to. You will see a path like “CUsersACK” where “ACK” is the username.
• You should know which of the user account is corrupted. Just look for a key named “RefCount” and change its Value data to “0” and click OK. And if it isn’t available, simply right-click on the right pane and create it.
• After that, double click on the key named “State” and make sure that the Value data is “0” and click OK.
• Exit the Registry Editor and restart your computer to apply the changes made and then check if it fixed the problem or not.

Option 5 – Run System Restore

• 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.

Error Code 16 - What is it?

Code 16 is a type of Device Manager error code. Windows XP users are most likely to encounter it. This error pops on XP systems that are running legacy or not plug-and-play hardware.

Error code 16 is displayed in the following format:

‘Windows cannot identify all the resources this device uses. (Code 16)’

Solution

Error Causes

Error code 16 occurs when you use a peripheral device such as an external drive or a printer and that device is not properly or completely configured. Though the device may have been recognized before Windows fails to verify its configuration. Simply put, error code 16 appears when devices are partially configured.

In addition to this, another cause of error 16 is outdated or corrupt device drivers. Devices often fail to run successfully because of driver problems.

Device drivers are programs that provide instructions to control different devices attached to the computer system such as audio devices and printers to name a few.

Though error code 16 is not fatal like other PC error codes such as BSoD; however, it may hamper your ability to use certain devices installed on your system and lower your work productivity.

To avoid inconvenience, it is advisable to resolve the error immediately to avoid inconvenience.

Further Information and Manual Repair

PC error codes are often considered technical and difficult to resolve which is why many prefer to hire a professional for the repair job rather than doing it themselves.

Small repair jobs like fixing error code 16 by a professional computer programmer may cost you hundreds of dollars.

So, why incur so much cost when you can repair it easily by yourself even if you are not a technical whiz.

Error code 16 is easy to repair.

Here are some effective DIY methods that you can use for resolving error code 16 on your PC. These methods require no technical background, knowledge or expertise for that matter. Just simply follow the instructions and resolve the error code 16 issue.

Let’s get started…

Method 1 - Setup from the Disk that Came with the Hardware Device

Run setup from the disk that came with the hardware device, or you can simply copy the setup software file to your hard drive/flash drive. Refer to the vendor’s direction to set up.

If for any reason you’re unable to find the directions, simply uninstall the device. Then go to the start menu, Control Panel, and select ‘Add New Hardware’.

Now pick the appropriate hardware and follow the steps that the Wizard suggests. This is most likely to resolve the error code.

Nonetheless, if the error code still persists, then try method 2.

Method 2 - Allocate More PC Resources

Another alternative method to resolve error code 16 is to allocate more PC resources to the device. To specify additional resources:

• Go to the start menu
• Type Device Manager
• Then go to the Device properties and click the resources
• Here specify the device in the Device Manager
• If you see a resource with a question mark, assign that resource to the device
• However, if for any reason the resource is unable to change, then simply click ‘Change Setting’.
• If Change Settings is not available, then click the box to the ‘Use Automatic Settings’ box. This will make the option available.

Method 3 - Install DriverFIX

As previously stated above, device manager error codes like error code 16 may also occur due to driver problems. If this is the underlying reason for error code 16 on your system, then the best way to resolve it is to install DriverFIX.

DriverFIX is user-friendly, advanced, and feature-filled software deployed with an intelligent programming system, which detects all problematic device drivers automatically in seconds.

It matches these drivers with their latest versions and updates them smoothly without any hassle, resolving error code 16 right away.

And furthermore, once you install this software on your PC, you don’t have to worry about driver problems anymore typically because it updates drivers on a regular basis with compatible and new versions, ensuring that your computer functions properly. It is easy to install and is compatible with all Windows versions.

Click here to download DriverFIX to repair error code 16

Although the Windows Updates do bring in new features and improvements, there are times when they also introduce issues as well. The main cause for these arising bugs is the incompatibility between the old and new software components. One of the issues brought in by such bugs is Clock is missing, invisible or black This problem was experienced by users after they recently installed a feature update. This particular bug can make the Windows clock in the taskbar appear to be black or invisible which makes it hard for users to read the time on their computers. According to experts, this bug has something to do with the Windows Themes and Aero styling. To fix this issue, here are some suggestions that could help but before you get started, you have to restart Explorer first and see if it can help in resolving the problem – if it didn’t, follow the options given below carefully.

Option 1 – Try to disable Custom Theme

It could be that the reason behind the black or invisible Windows Clock can be an old or an incompatible theme. You might have a custom theme in place and it became incompatible after an update. Thus, you can try switching to one of the default themes and then recreate your custom theme afterward. To do so, follow the steps below.

• Right-click on your desktop and select Personalize.
• Next, select Themes from the left menu and then select Windows 10 as your theme.
• After that, you can delete all the other custom themes and create them again from scratch. This should fix the black or invisible Windows 10 Clock.

Option 2 – Try to edit your existing themes

If you don’t want to get rid of your existing themes, there is an alternative solution you can try to fix the missing Windows 10 Clock albeit it’s a bit of a complex one. Follow the given steps below to modify the existing themes and fix the missing or black Windows Clock.

• First, you need to save your existing theme. Just simply right-click on your desktop and select Personalize and select Themes from the left menu.
• Next, click on the Save Theme button below your custom theme to save it. You can name the theme anything.
• After that, you can now modify the saved theme by going to C:/Users/UserName/AppData/Local/MicrosoftWindowsThemes.
• From there, look for the file with the theme name you just saved, and then right-click on the file and open it with notepad or any other text editing app.
• Now you have to look for the line that says, “Path=%SystemRoot%resourcesthemesAeroAeroLite.msstyles” and change it to “Path=%SystemRoot%resourcesthemesAeroAero.msstyles” and then save the file and rename it with some other name.
• Afterward, go back to themes and select the new theme you’ve created. This should resolve the Windows Clock issue as well as other Themes and Taskbar issues.

Option 3 – Try disabling the small icons in Taskbar

This option should help you fix any Windows Clock cases. So if your Windows Clock is nowhere to be found, you can try to disable small taskbar icons on your Windows 10 PC.

• Go to Settings > Personalization > Taskbar.
• From there turn off the toggle button for the “Use small taskbar buttons” option. Note that this solution is only a temporary one and it may or may not work in some cases.

Windows and Devices chief Panos Panay has revealed new focus sessions feature that will be in Windows 11 on his Twitter account today. He himself is referring to it as a game-changer especially with Spotify integration.

So what is a focus session?

From the video clip provided on Twitter, we can see that focus session users will be able to choose a specific task from the previously made task list, choose songs that will play in the background while the task is active, and set a timer for the chosen task with breaks. Maybe the best comparison and explanation would be a desktop google calendar task with music, basically, that’s it. A neat and good organizer inside your Windows 11 operating system. I think that this is generally a good idea and for sure it will find its audience.

Dune, arguably one of the best science fiction novels ever written was brought to a big screen first time by David Linch. Sadly movie itself went through development hell and a lot of troubles and the end result was somewhat strange. The audience was divided on it, some hated it, some loved it but for sure it left a mark in cinema history. Years have passed and just when people forgot about ever receiving another try on a book adaptation Denis Villeneuve has brought his vision of Frank Herbert's novel into its full glory on a big screen. The interesting thing about this new Dune movie was that from the start Denis envisioned it as a two-movie part openly saying that book itself is too complex to be done in a single movie. But, the issue arises when information about Dune part two was hanging on a thread on how well Dune part one will be received and performed in the box office. This naturally brought all kinds of speculation and worry among fans of the franchise, especially because the movie itself was really good and well made. Well for all of you fans and people who wanted to see a continuation of the story can rest at peace now since the Legendary picture has officially announced and green-lighted Dune part two. The budget was given and we can expect part two at the beginning of 2023.

If you are trying to install Microsoft Office on your Windows 10 computer but encounter an error code 30068 instead, read on as this post will guide you in fixing this problem. One of the causes of this error is an issue with the Office Click-to-Run service. It can also occur due to issues with the installation. And aside from the error code 30068, the error codes could also appear like this: 30068-29 (2), 30068-4 (3), 30068-4 (1715), 30068-39 (3), and many more. In most cases, the installation of Microsoft Office happens directly from the Microsoft servers which work via Click-to-Run service. This service is an alternative to MSI or offline installation. It is a Microsoft streaming and virtualization technology that helps in reducing the time that’s required to install Microsoft Office. Although it saves a lot of time, it also requires a good and stable internet connection for it to properly work. So if you encounter error code 30068 or any of the aforementioned error codes above when using this service, here are some potential fixes that could help.

Option 1 – Try to restart your computer and reinstall Office

The first thing you can do is restart your computer and then try installing Office again. It is possible that there’s some glitch and a restart might fix it. Once you’ve restarted your computer, install Office again. And if the online installation didn’t work, you can also try to download an offline Office setup.

Option 2 – Try checking if the Click-to-Run service is disabled

The next thing you can do is to verify if the Click-to-Run service is enabled or disabled. You can check its status in Services. How? Refer to these steps:

• Tap the Win + R keys to open the Run dialog box and then type “services.msc” in the field and tap Enter or click OK to open Services.
• Next, look for the Microsoft Click-to-Run service from the list of services and once you found it, double click on it.
• After that, go to the General tab and in the Startup type section, click on the drop-down menu and select Automatic.
• Then click on the Apply and OK buttons to save the changes made.
• Once you’re done, try to install Office again and see if the error is now fixed.

Option 3 – Try to uninstall and reinstall Office If neither of the two given options above worked, then you might want to uninstall Office and reinstall it. All you have to do is download the Microsoft Office Uninstall tool from the official site of Microsoft and run it. This will remove any incomplete Office installation as well as unwanted files. It will also get rid of all the Office apps and settings on your computer. This same option can be also applied if you encountered error code 30068-4 (3) when installing Office. On the other hand, if the Uninstaller tool throws an error that says, “Office installation is missing”, you have to check if there is an ongoing installation of Office.

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

Option 1 – Try to reinstall the program

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

Option 2 – Run System File Checker scan

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

• Hit the Win + R keys to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

 Reboot your computer.

Option 3 – Try checking the details in the Event Viewer

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

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

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

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

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

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

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

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

Option 6– Try to scan your computer using Windows Defender

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

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