HDMI Port not working properly in a Windows PC

One of the most sophisticated Artificial Intelligence or AI assistants there is in the market is Cortana. However, no matter how sophisticated this AI assistant may be, there are still times when you encounter issues with it. So if your Cortana is not connecting to the internet, worry not for this post will guide you in fixing the problem. This connection issue in Cortana might have something to do with the settings, network connectivity, or your Microsoft account. In addition, it could also be that the Firewall or antivirus program interferes with its connection. Whichever the case is, here are some possible solutions that could help you resolve the problem.

Option 1 – Try to power cycle the modem, router, and computer

• Connect the modem, router, and the PC hard-wired and then switch all of these three devices off.
• Turn on the modem and wait for 30 seconds.
• Turn on the router and wait for 30 seconds as well.
• Finally, turn on the computer and check if you can now successfully connect to the internet.

Option 2 – Check if your router or ISP is properly working

Since the basis for this issue is that Cortana is not connecting to the internet even though you are able to access websites using your browser, you might want to check your router or ISP (Internet Service Provider) and see if they’re functioning properly.

Option 3 – Try changing your internet connection

You can also try changing your internet connection and see if it fixes the problem. If you are using Ethernet, you can try connecting to a Wi-Fi connection and see if Cortana is able to connect or not.

Option 4 – Try to run the Search and Indexing troubleshooter

You might also want to run the Search and Indexing troubleshooter in Windows 10 as it checks whether the settings for Cortana are in place and automatically corrects any issues if the update or software installation has changed the settings. To run it just click on the Start button and select Settings > Updates and Security > Troubleshoot. From there, select the Search and Indexing Troubleshooter. Note: You can also run the Network Troubleshooter as it can also help in resolving the issue especially if the problem is in the network.

Option 5 – Try to remove Proxy

Removing the Proxy might also help you in fixing the connection issue in Cortana. Here’s how you can do it:

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

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

Option 6 – Verify your Microsoft account

In some cases, Cortana might not be able to connect to the internet because your Microsoft account is no longer verified. This usually happens when you use a two-step authentication system with your Microsoft account. To verify it, just open Settings and click on Accounts. After that, check if you have a Verify hyperlink under your Microsoft account or not then click on Verify. Afterward, follow the next on-screen prompts to verify your Microsoft account. Once your account is verified, restart your computer.

Option 7 – Try resetting Cortana

• Open Cortana and go to the Settings section where you’ll see the “Turning off Cortana clears what Cortana knows on this device, but won’t delete anything from the Notebook. After Cortana is off, you can decide what you’d like to do with anything still stored in the cloud” option. Turn this option off.
• Restart your PC.
• After your computer boots, launch Cortana again and check.

Option 8 – Try to reinstall Cortana

If none of the options given above works, you must consider reinstalling Cortana.

• First, right-click on the Start button and click on the Windows Powershell (Admin) option from the list.
• Next, type the following command and hit Enter to execute it:

Get-AppXPackage -Name Microsoft.Windows.Cortana | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}

• Restart your computer and check if Cortana is now able to connect.

In case you don’t know, there is a built-in tool in Windows 10, known as Reliability Monitor that provides a day-to-day snapshot of the health of your system. It warns users of any looming issues or disasters before your computer breaks down finally. So obviously, Reliability Monitor is useful, however, there are times when it could behave incorrectly. For instance, it might fail to show you any updates even when they are installed. Thus, if you experience any malfunctions with the Reliability Monitor tool in Windows 10, read on as this post will guide you in updating or working in Windows 10. To fix the problem with the Reliability Monitor, there are several fixes you can check out. You can try to enable the data collection for Reliability Monitor or reset it, as well as put your computer in a Clean Boot State. For more information, refer to each one of the options given below.

Option 1 – Try to enable the Data Collection for Reliability Monitor

The Reliability Monitor tool uses data provided by the RAC Agent scheduled task and it will start to display a Stability Index rating and specific event information 24 hours after the system installation. The RACAgent scheduled task, by default, runs after the operating system is installed. And if it is disabled, it must be manually enabled from the Task Scheduler snap-in for MMC or Microsoft Management Console. Thus, you need to enable the Data Collection for Reliability Monitor to fix the problem.

Option 2 – Try to reset the Reliability Monitor

The next thing you can do to fix the issue with the Reliability Monitor might want to reset it to resolve the problem. If the Reliability Monitor is already open, you have to close it and open it again. After the reset is done, it may take up to 24 hours for the Reliability Monitor to display results again. This should fix the problem.

Option 3 – Troubleshot the problem in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing the Black border issue. 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.

System image backup error 0x807800A1 & 0x800423F3 appears when you are trying to create a system image backup and the operation fails to do so. If you’re faced with any of these error codes, try our recommended solutions in the order presented below and resolve the issue.

Check Volume Shadow Copy & Software Protection Services

To restart the Volume Shadow Copy Service (VSS) on Windows 10, do the following:

• Press ⊞ Windows + X to bring up the Windows menu.
• Click on command prompt (admin)
• In the command prompt window, type the commands below and hit Enter after each line:

net stop vss net start vss

Once the commands execute successfully, try the system image backup again. The operation should complete successfully. You need to also check if the Software Protection Service is disabled. If it is, then Start it and ensure that it is set to default which is Automatic (Delayed Started).

Create System Image using PowerShell

Command lines are less prone to errors provided the syntax is correct, unlike GUIs that can suffer a glitch every now and then. To create a system image with PowerShell do the following:

1. Open the Windows PowerShell as administrator. To create a System Image in Windows 10 using PowerShell, you will have to run the Wbadmin command.
2. Inside the Powershell window type, then press Enter: wbadmin start backup-backup target: E:-include: C:-quiet-allCritical E: is the target drive where you’re going to save the system image, and C: is the system root drive where Windows is currently installed
3. To extract the created system image, starting over from Windows 10 USB installation media, select advanced startup or open run and type: C: \ Windows \ System32 \ Shutdown.exe / r / o

Use third-party imaging software

If the previous two solutions have not managed to solve the issue there is always an option to use a third-party imaging solution. There are free open source and buying options offering various advantages each. Find out which one works best for you and use it.

First time when your computer is turned ON and when Windows is booting it will wait 10 seconds before starting your startup applications. This 10 second is used to load all of Windows services so everything is running smoothly. If by any chance you do not want to wait for this startup delay and wish to start applications right away then keep on reading and follow this guide precisely. This guide will require you to play ad tweak with the registry of Windows, it is always recommended to make a registry backup before attempting any tweaks. Also, it is imperative to follow the guide as it is presented step by step. be aware that this guide will eliminate a 10-second delay for all of your starting applications, there is no way currently to remove delay for only one or a few.

1. Press ⊞ WINDOWS + R to open the run dialog
2. In run dialog type Regedit and press ENTER
3. Locate HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Serialize
4. If the key does not exist, make a new one,  Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\, right-click on the explorer and choose new > key. Name it Serialize
5. Right-click on Serialize and choose New > DWORD (32-bit) Value
6. Name the value StartupDelayInMSec
7. Double click on StartupDelayInMSec and locate Value data
8. Set the value to 0
9. Save changes and Exit Registry editor
10. Reboot

If you want to reverse changes and enable delay again, go back to the Registry Editor and delete the StartupDelayInMSec value.

The Windows 10 Telemetry and Data Collection features are auto-enabled and they collect all sorts of user activity and sends it to Microsoft. Microsoft says that the data collected only enhances the overall user experience and Windows functionality better but the number of data breaches happening across the globe has forced users to be extra cautious about their data privacy. So naturally, from stronger passwords and other services management, it is only logical to turn off Windows data gathering. To do so:

• Press ⊞ WINDOWS + R to open the run dialog.
• In the Run dialog type: taskschd.msc
• Press CTRL + SHIFT + ENTER key combo to open Task Scheduler in admin mode.
• On the left pane, navigate to the: Task Scheduler Library > Microsoft > Windows > Customer Experience Improvement Program
• At the location, on the middle pane, right-click on the task named Consolidator and select Disable from the context menu...
• Repeat the process with all other tasks listed in the middle pane.
• Exit Task Scheduler.

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.

nVIDIA is one of the behemoths of the GPU world, but that not means that they are perfect and that they do not make mistakes, throw WIndows in the mix, and sometimes you have issues with your nVIDIA display drivers for various reasons which could get very unpleasant. But do not worry, we have your back and in this article, we will focus and help you to resolve common nVIDIA driver issues. So sit back and let's start with the repairs.

1. Rollback to the previous driver and stop automatic updates.

   nVIDIA sometimes publishes really messy drivers which can really cause some serious issues, if by any chance you managed to be unlucky enough to get this kind of driver, do not despair, roll back to the previous working version and wait for the fix. To stop Windows from doing automatic driver updates, navigate to Control Panel > System & Security > System > Advanced System Settings > Hardware > Device Installation Settings. Then choose "No (your device might not work as expected)". Once you have turned off automatic driver updates, uninstall your current driver and install the previous version from the official nVIDIA website. Reboot your system

2. Reinstall nVIDIA driver

   Reinstalling the driver might fix the issue if by any chance driver files got corrupted during download for example. First, you will need to delete some files in order to perform a clean installation. Log in as administrator if you are not one and delete following files and folders: C:\Windows\System32\DriverStore\FileRepository\nvdsp.inf fileC:\Windows\System32\DriverStore\FileRepository\nv_lh fileC:\Windows\System32\DriverStore\FileRepository\nvoclock fileC:\Program Files\NVIDIA Corporation\C:\Program Files (x86)\NVIDIA Corporation\Reboot your system Start driver installation again, choose custom installation, then clean install.

3. Update driver in the Device Manager

   If driver updates for any reason can not work via the official install package from nVDIDA, try updating the driver in the Device Manager Navigate to Device Manager, expand graphic adapters, right-click on your nVIDIA device and click on update driver. Reboot your system

That's it, 3 solutions on how to remove, reinstall and update your nVIDIA driver, thank you for reading and I hope to see you again.

When you encounter an error message that says, Chassis Intruded…Fatal Error…System Halted on your monitor then it indicates that the Chassis or the cabinet that holds the CPU, GPU, motherboard, and many more is open. It is a security feature offered by OEMs wherein a connector that is found in the motherboard can detect if the chassis component has been replaced or removed. There are a few OEMs that offer onboard speaker or PC chassis speaker which goes off in this kind of situation. Obviously, the problem has something to do with the hardware and in most cases, you have to put the jumper back on the motherboard with the pin-labeled chassis signal and ground. There are times when some OEMs offer a simple switch that is armed automatically when you properly close the chassis. Thus, you need to check if this switch has something to do with the error. If there is no switch or if it doesn’t resolve the issue, although you may be able to get into Windows with a warm boot, the normal Windows boot won’t really work unless you fix the problem. It is rather false positive and has something to do with the RTC RAM state or the BIOS. You might need to completely disable the Chassis intrusion feature to fix the error. Refer to the suggestions given below to try and fix the “Chassis Intruded, Fatal Error … System Halted” error.

Option 1 – Try to clear CMOS

You can easily clear CMOS by shorting two pins which can be found side by side on the motherboard. Keep in mind that it may vary from OEM to OEM although the basics are still the same to clear CMOS. In addition, you might also have to download the manual from the OEM’s website so that you’ll know its exact location.

Option 2 – Try booting into the BIOS

You can also try booting into the BIOS. All you have to do is tap either the DEL or F2 keys to get there. Note that everything will be set back to their default setting after you reset the CMOS.

Option 3 – Try disabling Chassis intrusion

In this option, you have to look for the Chassis intrusion feature in your BIOS. It might be located under security. From there, disable it and check if the problem’s fixed.

Option 4 – Try to reconfigure the BIOS

Once you have disabled the Chassis feature, you need to reconfigure the BIOS the way you expect it to be or to what it was before the reset.

Microsoft has officially announced details about the newest upgrades to its office 365 suite moving forward along with its new OS release. It seems that Microsoft has listened to its user base and feedback since Word, Excel, and PowerPoint are getting much-needed redesign taking into account many suggestions from the community. The new office should feel more like an application suite guiding focus on the interconnection of applications themselves providing users with a much more natural experience of using them.

The new office features so far

From Microsoft themselves:

“This Office visual refresh is based on feedback from customers who asked for a more natural and consistent experience within and between your applications, specifically on Windows. With this update, we deliver an intuitive, coherent, and familiar user interface, using the Fluent Design principles, across all your applications: Word, Excel, PowerPoint, OneNote, Outlook, Access, Project, Publisher, and Visio. We aligned this visual refresh with the design of Windows 11 to provide seamless experiences on your PC.”

It is always refreshing to hear when a company listens to its user base and actually does what is needed instead of trying to invent the wheel.

How to switch

Since beta is already rolling and if you have an active 365 subscription to office suite visual refresh will be automatically available to all Office insiders running beta channel builds. It can be turned on and off using the coming soon feature in the top right corner of the menu in any application. Just click on the megaphone icon to open the coming soon pane and apply settings to all office apps. Note that The Coming Soon feature is not available in Access, Project, Publisher, or Visio. If you turn on the visual refresh in any of the 4 apps mentioned above (Work Excel, PowerPoint, or OneNote), it will also be available in these 4 apps.

Difference themselves

The Home tab menu still has a familiar look with a few tweaks. For example, accessing frequently used Word commands will be a lot easier. By navigating to Designer > Show Quick Access Toolbar, users can add a customizable shortcut ribbon to Word that houses conveniently placed options. Also, the office will not match your Windows operating system color theme so if you have a dark theme enabled, the office will also have a dark color theme. Color palettes are more neutral, corners are a bit softer but customizable ribbons are a win here for me.

Conclusion

There was not much said other than visual upgrades and small tweaks that were supposed to make your life easier but then again Windows 11 itself is in the same boat. I am not sure if this is a great update offering just some visual tweaks and focus on workflow mechanics or just being plain lazy and trying to cash in visuals as a completely new product.

If you suddenly find the Windows Recovery Environment not working and you see an error message saying, “Could not find the recovery environment”, then you’ve come to the right place as this post will guide you on how you can fix it. In times when you can’t boot into the Windows Recovery Environment, there could be several reasons behind it. However, have you ever wondered where exactly the Windows Recovery Environment is in your computer? Windows initially places the Windows RE Image file in the installation partition during Windows Setup so if you have installed Windows in the C drive, you can find the Windows RE at the C:/Windows/System32/Recovery or C:/Recovery folder. Keep in mind that this folder is hidden and later on, the system copies the image file into the recovery tools partition to make sure that one can boot into recovery if there are any issues with the drive partition. The “Could not find the recovery environment” error mostly occurs if the Windows Recovery Environment is disabled or if the “Winre.wim” file is corrupted. Thus, to fix this error, you need to refer to the given suggestions below.

Option 1 – Try to enable Windows Recovery Environment

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• Next, type the “reagentc /info” command and tap Enter to execute it.
• After that, if the output states that Status is enabled, then you’re all set.
• Now type the “reagentc /enable” command and tap Enter to enable the Windows Recovery Environment. You will see a success message at the end signifying that Windows RE is available.

Option 2 – Try to fix the corrupted or missing “Winre.wim” file

If the Winre.wim file is either corrupted or missing, you need to get a new copy of this file from another computer where the Windows RE is working. Once you’re able to get a new copy of the Winre.wim file, you have to set the image path to a new location. For more details, refer to these steps:

• First, type “Powershell” in Windows Start Search and right-click on Windows PowerShell from the results, and select Run as administrator.
• Next, execute the given command below to change the path of the WIM file to the new location. Note that the steps should be used when the file path of the Windows Recovery Environment is different from the usual spot.

Reagentc /setreimage /path C:RecoveryWindowsRE

• As mentioned, if the file is corrupted, you just have to get a new copy from another PC but before you do that, make sure that the WINRE on that computer is disabled (just enable it later on) and then place it in the C:/Recovery path and then set its path again using the command given above and then verify its path by executing the following command.

reagentc /info command

Note: Since the Recovery folder is hidden as well as the WINRE folder in it and you won’t be able to access them using the Windows File Explorer, you need to use the Windows PowerShell or Command Prompt so that you can access them.

Option 3 – Try checking and fixing the WinRE Reference in the Windows Boot Loader

The Windows Boot Loader is the one that determines if it has to load the Windows Recovery Environment. It could be that the boot loader is pointing to an incorrect location which is why you’re getting the error. To resolve it, you have to check and fix the WinRE Reference in the boot loader. How? Follow these steps:

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• After that, execute the “bcdedit /enum all” command.
• Next, look for an entry in the Windows Boot Loader identifier set as Current and look for “recoverysequence” in that section and take note of the GUID.
• Ensure that the device and the osdevice items show the path for the Winre.wim file and that they are the same. If not, you need to point the current identifier to the one which has the same.
• Once you’ve found the new GUID, execute this command: bcdedit /set {current} recoverysequence {GUID_which_has_same_path_of_device_and_device}
• Now check if the error in the Recovery Environment is fixed or not.

Option 4 – Try creating a Recovery Media

You could also try creating a Recovery Media to resolve the error in the Windows RE. All you have to do is download the Windows 10 ISO file using the Media Creation tool and then create a recovery drive. Once you’re done, check if it fixes the problem or not.