How to Fix Runtime Error 713

If by any chance your search result in Windows is misleading, missing, or incorrect then it is a high probability that your search index is out of date. To repair this issue follow this guide step by step. Please take note that rebuilding the whole search index can take a long time on some systems depending on the size of the index itself, CPU speed, HD speed, etc. Sometimes it can take even hours on large drives. First, press ⊞ WINDOWS + R to open the run dialog and type in it Control panel to open the control panel. Once you are in the control panel, switch your view to large icons and locate Indexing options. Inside indexing options, click on advanced. In advanced options click on the rebuild and confirm. Leave your computer to finish and your searches should be working fine now.

In case you don’t know, the Windows Registry contains a System Hive which is a core part of Windows. The Windows operating system store various settings, options, and configurations. And if you encounter a Device Manager Error 49 for a device then it means that the system hive has exceeded its size limit. Worry not for this post will provide you with possible solutions that can help you in fixing error code 49. You will see the following error message when you encounter error code 49:

“Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit), (Code 49)”

There are instances when it may so happen that the device or devices are no longer attached to the computer but they are still listed in the system hive of the registry. For instance, if you were removing hardware and application for years but they weren’t removed from the registry then the size of the system hive keeps on growing until it hits the maximum limit. As you know, making changes in the registry manually, no matter how knowledgeable you are on such things is not sage since the registry is not only important but also complex. In addition, the System Hive is also a permanent part of the Registry associated with a set of files that contain information related to the configuration of the computer on which the OS is installed. To resolve this error, you must remove or uninstall any hardware devices that are no longer in the system. In fact, the Device Manager hides them by default so you need to enable hidden or non-present devices. Follow the instructions given below to set the Devices Manager to display devices that are no longer connected to the computer. Step 1: Tap the Win + R keys to open the Run dialog box. Step 2: After that type in “cmd” and hit Enter to open the Command Prompt. Step 3: Type “set devmgr_show_nonpresent_devices=1” in the Command Prompt and hit Enter to enable the hidden devices option. Step 4: After that, exit Command Prompt and tap Win + X + M to open the Devices Manager. Step 5: After opening the Devices Manager, click on View and then select the “Show hidden devices” option. This will show you all the devices that are not connected to the computer but are still mentioned. Step 6: Next, select a non-present device and click Uninstall from the Driver tab. Step 7: After that, repeat what you’ve done on step 5 for any other device that you no longer use. Step 8: Restart your computer. You can check the device Properties dialog box in the Device Manager after you’re done removing all the useless devices, to check if the error is now fixed or not. Moreover, you can also try running the Hardware and Devices Troubleshooter as it can also help resolve hardware-related problems. To use it, refer to the steps below.

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

In case you don’t know, Microsoft has included an Enhanced Search Mode in the new Windows 10 v1903. This new Enhanced Search mode, compared to the Classic Mode, indexes everything on your Windows 10 computer, and in this post you will be guided on how you can disable this new feature as well as discuss how it is different from the Classic Search mode. Over the years, the Windows 10 Start Search has changed. When you tap the Start button and when you type, the results that appear are categorized into Apps, Documents, Email, Web, Folders, Music, People, Photos, Settings, Videos, and many more. This is the reason why the Enhanced Mode was brought into the picture. So unless everything is indexed, this new feature wouldn’t be of much use. A Classic Search is the term used for the old search technique in Windows 10. The Classic Search mode is restricted to Libraries and Desktop and end-users can only select to customize the search location by adding them manually to the indexer. To simply put it, it would only index files and folders which you want to get indexed and if the search term is not in the index, it would initiate the regular search which would take quite a while and this is where the Enhanced Windows Search comes in. It indexes everything as it is its default nature which is the exact opposite of the Classic Search mode. This feature allows you to exclude folders where the Search will not look and index anything that could be personal to you. In addition, it can also impact the life of the battery of laptops, if you are using one. The initial crawl of your data will take place only when connected to power and during that time, both the CPU usage and battery will take a bit of a hit.

To enable the Enhanced Search Mode in your Windows 10 computer, here’s what you have to do:

Step 1: Go to Settings > Search > Searching Windows. Step 2: Next, click on the radio button for Enhanced. Step 3: After that, select the folders which the Windows Indexer should exclude from the Enhanced Search mode. And that’s about it. The next time you search anything on your computer, Windows will be looking at all the locations except for the ones you excluded and the results will be a lot faster compared to the Classic Search. Now that you’ve enabled the Enhanced Search mode, there are two settings you need to check out.

• Advanced Search Indexer Settings – this setting allows you to configure how or where Windows will search or what file types it will search in your computer. It will also open the same setting that’s available in the Classic Search.
• Run the Indexing Troubleshooter – when you click on the Indexing Troubleshooter, it will start to troubleshoot any Search and Indexing issues on your Windows 10 computer and fix them automatically.

Recently, a number of users reported that they were not able to use the “Run as administrator” context menu option when they tried using it or opening a program with administrator privilege. If you are one of these users facing this problem, then you’ve come to the right place as this post will guide you in fixing this issue. At the time of writing, it isn’t clear what the cause of the issue is but there are potential fixes you can try to fix the problem. You can try turning on the User Account Control or clean up the Context Menu items change the Group Membership. On the other hand, you can also perform both SFC and DISM scans via Command Prompt or troubleshoot the problem in a clean boot state as it is possible that some third-party programs are the ones that are causing the problem. You could also run an anti-malware scan using Windows Defender or your antivirus program.

Option 1 – Try to turn on the User Account Control

When you open a program with administrator privilege, the User Account Control or UAC prompt will pop up asking you to confirm the permission. However, if you have disabled the User Account Control by mistake or some malware has disabled it, then it’s no wonder why the “Run as administrator” option is not working. Thus, you need to check if UAC is turned on or not. All you have to do is go to the User Account Control settings.

Option 2 – Try changing the Group Membership

• First, you need to sign in with your administrator account or ask your administrator to sign in for you. So if you only have a Standard User account, you have to add that account to the Administrators group.
• In the taskbar search box, type “netplwiz” and check the search results.
• From there, select your user account and click the Properties button.
• After that, go to the Group Membership tab and select Administrator.
• Now click on the Apply and OK buttons to save the changes made and then sign in to your computer again and see if the “Run as administrator” option is working or not.

Option 3 – Try to create a new Administrator User account

If you have a standard account, you can try creating a new account but this time, you create an administrator user account and then see if you can now use the Run as administrator option or not. Note that you have to sign in with your main account before you can create an admin account.

Option 4 – Run the DISM tool

You can run the DISM tool as well to help fix the problem with the “Run as administrator” option. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 5 – Perform a System File Checker scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the problem with the “Run as administrator” option on your Windows 10 computer. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

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

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.

• Once done, restart your computer.

Option 6 – Put your computer in a Clean Boot State

You can also troubleshoot the problem in a Clean Boot state. It could be that there are some third-party applications in your computer that are preventing you from using the “Run as administrator” option and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try to use the Run as administrator again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• 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.)
• After you’ve set your computer into a Clean Boot State, try to check if the error is now fixed and that you can now view the Properties.

Option 7 – Try scanning your computer using Windows Defender

As mentioned, if your computer was recently infected with some malware, it is possible that the malware changed the User Account Control settings which is why you’re not able to use the Run as administrator option. Thus, you need to scan your computer using 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.

If you suddenly receive an error saying, “Error 105 (net:: ERR NAME NOT RESOLVED): Unable to resolve the server’s DNS address” when browsing the web, then this means that the DNS lookup has failed. This kind of error is one of the most commons ones you can encounter while using the Chrome browser. And since it’s a pretty common error, the solutions for this one are pretty easy as well.

Option 1 – Disable both the Antivirus and Firewall temporarily

There are times when antivirus programs and the firewall blocks a website that they consider to be malicious or even because of false-positive effects. Thus, you need to disable these programs temporarily as it might be the reason why you’re getting the “Error 105 (net:: ERR NAME NOT RESOLVED): Unable to resolve the server’s DNS address” error in Chrome.

Option 2 – Check the Network Cables and restart the router then reconnect

Of course, the next thing you have to do is to check if the network cables connected to your computer or router are properly connected. And if your computer is connected via Wi-Fi, you need to make sure to restart your router once. In addition, you can also forget the Wi-Fi your computer is currently connected to and then try reconnecting again to see if it would work.

Option 3 – Try running the Chrome Cleanup tool

You might want to run Google Chrome’s built-in Malware Scanner & Cleanup tool as it could also help in getting rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and anything else that might overtake the network and could affect the performance of the browser.

Option 4 – Try removing the Proxy

Removing the Proxy might also help you in fixing the ERR_NAME_NOT_RESOLVED error in Chrome. 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 5 – Disable Prefetch in Chrome

In case you don’t know, Google makes use of a prediction service that helps users in completing searches and typing URLs in the address bar. This prediction service uses the already resolve IP address to connect to the website you’ve already visited. Thus, it would be better if you disable it in cases like this one.

• Open Chrome’s Settings.
• Next, go to Privacy and Security then look for “Prefetch”.
• After finding Prefetch, toggle off the “Use a prediction service to help complete searches and URLs typed in the address bar” setting and then restart Chrome.

Option 6 – Flush the DNS, reset Winsock and then reset TCP/IP

• Click the Start button and type in “command prompt” in the field.
• From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After opening Command Prompt, you have to type each one of the commands listed below. Just make sure that after you type each command, you hit Enter
  • ipconfig /release
  • ipconfig /all
  • ipconfig /flushdns
  • ipconfig /renew
  • netsh int ip set dns
  • netsh winsock reset

After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.

Option 7 – Try using the Google Public DNS

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8” and “8.8.4.4” and click OK and exit.

Option 8 – Reset Chrome

Resetting Chrome can also help you fix the error. Resetting Chrome means restoring its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up the option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

The ntkrnlmp.exe file is a file associated with the Windows operating system’s NT Kernel and other system processes. It is also related to the “CRITICAL PROCESS DIED” error. So if you encounter a Blue Screen of Death error that’s related to this file, then you’ve come to the right place as this post will guide you in fixing the ntkrnlmp.exe Blue Screen error. This kind of Blue Screen error might be caused by the file getting corrupted or infected with some malware. Aside from these causes, the error might also be due to the corruption and malfunction of the graphics card drivers. Before you troubleshoot the problem, you might want to try performing System Restore especially if you tend to create a System Restore point every now and then. Performing System Restore could help you resolve the ntkrnlmp.exe Stop error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If System Restore didn’t help, then proceed to the given options below.

Option 1 – Disable the C-states and EIST in the BIOS

The first thing you can do is try to disable the C-states and EIST in the BIOS. To do that, refer to the steps given below.

• Go to the BIOS and from there look for an option named CPU Configuration which can usually be found under the Advanced menu.
• Next, look for CPU Power Management and under that section, disable both the “Intel EIST” and “Intel C-state” options.
• After you disable them, save the changes you’ve made and exit the BIOS.
• Now restart your computer and check if the ntkrnlmp.exe BSOD error is now fixed.

Option 2 – Try to update, rollback or disable drivers

If the first option didn’t help in fixing the ntkrnlmp.exe Blue Screen error the next thing you can do is to roll back, or update, or disable device drivers in your computer. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

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

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

Option 3 – Configure the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues. And so if you want to fix the ntkrnlmp.exe Blue Screen error you need to use the Driver Verifier Manager:

• Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
• After that, select the option “Create custom settings”.
• Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
• Next, select the option “Select driver names from a list” option.
• Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
• Then click on the Finish button.
• Open Command Prompt as administrator and execute this command – verifier /querysettings
• The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
• Open the Command Prompt as admin again and run this command – verifier /reset
• The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 4 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like ntkrnlmp.exe. 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.

There are times when an IT admin has to set up multiple IP addresses to the same network adapter. Setting up multiple IP addresses in scenarios like hosting various SSL sites, speed up traffic exchanges can help in avoiding being blacklisted in the SPAM filters, and so on. So in this post, you will be guided on how exactly you can assign multiple IP addresses to the network adapter in your Windows 10 computer. There are several ways to assign multiple IP addresses in a network adapter. You can do it using the Network Adapter settings or using the Netsh utility, as well as the Windows PowerShell utility. To get started, refer to each one of the options provided below.

Option 1 – Assign multiple IP addresses via Network Adapter settings

• Go to Settings first and from there, select Network & Internet, and then click on the Change adapter options. This will show you a list of both the physical and virtual network adapters in your computer.
• Next, double click on the Ethernet adapter where you want to assign the multiple IP addresses and then click on the Properties button.
• After that, you should see the Ethernet properties where you have to select the “TCP/IPv4” or “TCP/IPv6”.
• Once done, click on the Properties button and then select the “Use the following IP address” option under the General tab.
• Now you have to add an IP address, subnet, and default gateway to the network adapter and then click on the Advanced button.
• This will open the Advanced TCP/IP settings where you have to click on the Add button so you can add an IP address. From here, you can keep adding multiple IP addresses to the network adapter. You also have the option to add multiple gateways or DNS IP addresses.
• Once done, if you execute the “ipconfig” command, you should see all the secondary IP addresses listed.

Option 2 – Assign multiple IP addresses using the Netsh command

Another way to assign multiple IP addresses to your network adapter is via the Netsh command.

• In the Start Search, type “command prompt” and from the search results that appear, right-click on Command Prompt and then select the “Run as administrator” to open it with admin privileges.
• If a User Account Control or UAC prompt pops up, just click on Yes.
• After that, run this command: Netsh int ipv4 add address name="Local Area Connection" 192.168.100.100 255.255.255.0 SkipAsSource=True

Note: You have the option to set “SkepAsSource” since it depends on your needs using the Netsh command. When it is configured as true, the IP address won’t be used by the OS for outbound connections.

Option 3 – Assign multiple IP addresses via Windows PowerShell

• Tap the Win + X key combination and click on the “Windows PowerShell (Admin)” option.
• After opening Windows PowerShell as admin, use the NetIPAddress command so you can add more IP addresses. Execute this command: Get-NetIPAddress | ft IPAddress, InterfaceAlias, SkipAsSource
• Next, assign an IP address to a network adapter by executing this command: New-NetIPAddress –IPAddress 192.168.100.100 –PrefixLength 24 –InterfaceAlias “vEthernet” –SkipAsSource $True
• Now to modify the “SkipAsSource” parameter, use this command: Get-NetIPAddress 192.168.100.100 | Set-NetIPAddress -SkipAsSource $False

Virtual Reality is slowly becoming standard in gaming. More and more affordable headsets are coming out lowering entry prices and making them affordable for all. But in a sea of new VR headsets, it is important to at least purchase a decent one that will perform nicely and hopefully last longer. Therefore in today’s article, we will address some of the best options currently available on the market,

Oculus Quest 2

With its Rift model, Oculus set itself as a big player in VR. Now the company is slowly bowing out of the dedicated, tethered VR headset with its latest Quest 2 designed to primarily be a standalone headset. In case you do not know, tethered headset means that the headset itself is connected to your PC and is using its power to drive your VR experience. Now technical specifications of Quest 2 are pretty OK and it can drive stuff pretty decently and if you want you can purchase the dedicated cable to connect it to your PC for the full experience of games requiring more capable hardware. Oculus Quest 2 is the cheapest headset on this list and with its stable performance, is highly recommended.

Valve Index VR

Although the headset itself is nothing revolutionary or special its controllers are. They can track individual finger movements, making games (that take advantage of them) much more immersive than the standard trigger grips on other controllers. The Index's higher refresh rate makes for smoother action, as well, which is another nice bonus. If you already have an HTC Vive or Vive Cosmos Elite, and their base stations (not the regular Cosmos), you can buy only the controllers.

Sony PlayStation VR

The PlayStation VR is compelling thanks to Sony backing its development, plus the PlayStation 4's affordability and availability compared with gaming PCs. All you need is the headset, a PlayStation 4, and a PlayStation Camera (now included with most PlayStation VR bundles). Not really the best of the bunch but still one of the top ones for console gaming. Sony is working on a new PlayStation VR system for the PlayStation 5, with redesigned controllers. The new headset hasn't been revealed yet, but the company has released a preview of the new controllers.

HP Reverb G2 VR

HP headset is one which you get if you want the best image quality in VR headset, sadly controllers did not follow the same quality of headset itself. But this is still a pretty decent headset overall and worth the purchase.

HTC Vive Cosmos

HTC's Vive Cosmos is the upgraded version of the Vive. It features a higher resolution and replaces the external base stations with outward-facing cameras for motion tracking. It's a comprehensive package for whole-room VR. HTC recently released the Vive Pro 2, a high-end VR headset targeting both enterprise users and consumers. This new headset features a 2,448-by-2,448 resolution display for each eye, making it the highest-resolution headset currently available. It's also more expensive than the Cosmos Elite. Sadly one thing that is bringing this headset down is the price.

After you fresh install Windows 10 on your computer, it allows you to set up a PIN just before you can start using it. However, a number of users reported that the Windows 10 installation gets stuck on the “Set up a Pin” phase. If you are one of the users who experience the same thing, then read on as this post will walk you through fixing the problem. As users start to use their newly installed Windows 10 computer, they reported that the screen is still stuck even after they enter the correct PIN twice and there is no way for them to go forward or backward. Note that this is a part of the account setup and that your computer must stay connected to your internet connection before you finalize everything. And even though the PIN works when the computer is offline, the account setup still needs an internet connection, at least for a fresh installation. The solution for this kind of issue is quite easy and there won’t be any problem even if your computer shuts down or restarts since the installation is already complete and all that’s left is the account setup. To fix this problem, follow the steps given below. Step 1: The first thing you have to do is to turn off your internet connection or disable all connectivity from your computer. Note: If you are using either an Ethernet cable or a Wi-Fi switch to connect to the internet, you have to disable or remove them. But if you don’t have any options, just completely turn off your internet connection. Step 2: The next thing you have to do is to force your computer to shut down and then restart your computer. The setup process will eventually pick up exactly where it left off. The only difference is that there is no connection to the internet and your screen will no longer be stuck on the PIN setup screen so you now have the option to skip it and wait until you’re logged in for the first time. Step 3: Once you’re done, you can then you can choose to Setup Pin later on and turn your internet connection back on or connect your computer with an internet connection.

Runtime Error 713 is an error that occurs during the distribution of a Visual Basic application that includes a data report. The error is displayed on the screen when you try to open the data report from your desired application.

Error Causes

The reason why computer users often experience the Runtime Error 713 is that the data report run-time file also referred to as Msdbrptr.dll is not included in your setup package. Though this error does not pose any big threat to your computer, however, it is recommended to fix the error because the Runtime error 713 may hamper your ability to install and access new programs.

Further Information and Manual Repair

Don’t you panic if you see Runtime Error 713 message pop up on your PC? This error is rated easy to repair and can be fixed in a couple of minutes. There are two ways to fix Runtime Error 713. You can choose whichever 2 alternatives suit you best.

• Method 1

First, open your project and include a reference to the data report file, the Msdbrptr.dll file. Locating this file is not difficult. It is listed as Microsoft Data Report Designer v6.0 in the reference dialog box. Sometimes you may see this file listed more than once. Now when this happens be sure to select the file that is associated with Msdbrptr.dll. After you select it, the reference will be verified. Once verification is complete, you are good to go. Now you can try rebuilding your setup package again.

• Method 2

The second alternative is to add the Msdbrptr.dll file manually in PDW (the Package and Deployment Wizard). Simply add the file in the Included Files dialog box window and run the PDW. Now you are all set to rebuild your setup package. Whether you follow method 1 or 2 after you rebuild the setup package and the installation is complete, you will see the following files in the indicated folders:

• <windows system>Msdbrptr.dll
• <program files>Common Files\Designers\Msderun.dll
• <windows system>Msstdfmt.dll

The presence of these files indicates successful installation and now you can easily try opening the data report. If you’ve noticed, all you have to do to fix Runtime Error 713 was to include the Msdbrptr.dll file. So, next time if you or your friends experience Runtime Error 713, you know exactly what to do and how to fix it.