FIX: there’s a problem with the clipboard by Bas Wijdenes

There’s a problem with the clipboard, but you can still paste this content within this workbook.

Excel and other Microsoft Office applications have their own clipboard function. Within Microsoft Office you can copy the formatting or paste it as plain text. Excel displays this message “There’s a problem with the clipboard, but you can still paste your content within this workbook” after you try to copy something because another program is using your clipboard. You can still copy and paste you can only copy to other programs, but no Microsoft Office programs.

There's a problem with the clipboard, but you can still paste your content within this workbook
There’s a problem with the clipboard, but you can still paste your content within this workbook

There is no complete solution to this problem unless you can find out which program kidnapped your clipboard. I did find a workaround to turn off the notification in Excel.


Workaround

Short guide
  • Start Excel.
  • Go to File in the upper-left corner.
  • Click Options.
  • Go to General.
  • Under User Interface Options un-check Enable Live Preview.

You shouldn’t be getting the message now.


Long guide

Click on Start and search for Excel.

There's a problem with the clipboard, but you can still paste this content within this workbook
There’s a problem with the clipboard, but you can still paste this content within this workbook

Go to File in the upper-left corner.

There's a problem with the clipboard, but you can still paste this content within this workbook
There’s a problem with the clipboard, but you can still paste this content within this workbook

Open Options at the bottom of the menu.

There's a problem with the clipboard, but you can still paste this content within this workbook
There’s a problem with the clipboard, but you can still paste this content within this workbook

Find Enable Live Preview under User Interface Options and uncheck it.

There's a problem with the clipboard, but you can still paste this content within this workbook
There’s a problem with the clipboard, but you can still paste this content within this workbook

If you do have a real solution , please let me know this in the comments and I’ll update the blog post.

Configure a send only mailbox by Bas Wijdenes

Send only mailbox the basics

Nowadays a send only mailbox usually occurs in Exchange. This can be  Exchange Online (Office 365), but also Exchange On-Premise. The first method is about creating a Send Only Mailbox in Exchange.

It’s also possible that you’re using other mail applications such as Google Apps. Unfortunately my knowledge does not extend so far to know if you can create rules within the G Suite Admin Console. The second method is about configuring a Send Only Mailbox in Outlook itself.

A send-only mailbox can be useful if you want multiple users to work from one address that only send mails. This can for example be a no-reply address.


Method 1 – Create a send only mailbox in Exchange

In method 1 I explain how you can create a send only mailbox. Most users will call this a no-reply mailbox or something similar.

I assume that you are an IT engineer and therefore already know how to get to the rules within the Exchange platform.

  1. Create the mailbox in the regular way.
  2. Go to Exchange and open the rules. You can open this link for Exchange Online.
  3. Click on the +> Create a new rule
  4. Open More options…
  5. Name the rule whatever you like. I’ll call it Send-Online-Mailbox
  6. Select Apply this rule if the recipient is…
  7. Select Block the message..
    Here we can choose what we want to do with the received mail. If it is a no-reply email you could send back an answer that it is an unread mailbox or something similar.
    I choose delete the message without notifying anyone.

    No-Reply send only mailbox
    No-Reply send only mailbox
  8. Use the default settings for the rest.
  9. Click Save

Below is the entire rule for clarification:

No-Reply send only mailbox
No-Reply send only mailbox

Now all you have to do is give users permissions to the mailbox and open them in Outlook or OWA. From now on users can only send e-mails and no longer receive them. For these mailboxes it is useful to add an extra disclaimer so that the recipient knows that this is a no-reply address.

Method 2 – Configure a send only mailbox in Outlook

If you use a different mail application than Exchange, for example G-Suite or use a mailbox in cPanel or something similar, you can also configure a send only mailbox directly in Outlook.

The steps that we configure here are unfortunately adaptable unless you implement this via a Group Policy. I have not done this myself before through a Group Policy.

  1. Go to Control Panel and search for Mail.
  2. Click Add
  3. Select Manual setup or additional server types
  4. Click Next >
  5. Select POP
  6. fill in your name, e-mail, and credentials and select POP3
  7. Fill in an incorrect incoming mail server.
  8. Use the correct Outgoing mail server (SMTP).
  9. As an example, for gmail it’s smtp.gmail.com.
  10. Fill in your email address and password
  11. Uncheck Automatically test account settings when Next is clickedNo-reply send only mailboxNo-reply send only mailbox
  12. Click Next
  13. Click Finish
  14. Start Outlook
  15. Press CTRL + ALT + S on your keyboard
  16. Click EditSend only mailbox OutlookSend only mailbox Outlook
  17. Uncheck Receive mail itemsSend only mailbox OutlookSend only mailbox Outlook
  18. Click OK

Install Windows 10 in VirtualBox by Bas Wijdenes

Setting up Windows in VirtualBox

I started looking at this blog post again and its content is still relevant.

In this tutorial I explain how to install Windows 10 or earlier versions in VirtualBox. VirtualBox is a virtualization tool to run virtual machines from Windows to another OS on your local Device.

For more about VirtualBox please go to their website.


Install Windows in VirtualBox preparation

First we’ll have to download VirtualBox.
click here for a direct download, or go to their website to download VirtualBox manually: Download

Use the Windows Media Creation Tool to create a Windows 10 ISO.

The system requirements for Windows 10 are:

  • Processor: 1 gigahertz (GHz) or faster
  • RAM: 1 gigabyte (GB) (32-bit) or 2 GB (64-bit)
  • Free hard disk space: 16 GB
  • Graphics card: Microsoft DirectX 9 graphics device with WDDM driver
  • A Microsoft account and Internet access

Install Windows in VirtualBox tutorial

Installing VirtualBox

Go to configuring VirtualBox for Windows 10 if you’ve already installed VirtualBox.

After you’ve downloaded VirtualBox we can start installing VirtualBox.

Start the setup by double-clicking the setup.exe
Click Next

Install VirtualBox
Install VirtualBox

Use the standard settings to make the best use of VirtualBox.
Click Next

Install VirtualBox
Install VirtualBox

Use the desired settings and leave the register setting checked.
Click Next

Install VirtualBox
Install VirtualBox

The next screen shows us a warning:

“Warning: Network Interfaces

Installing the Oracle VM VirtualBox Networking feature will reset your network connection and temporarily disconnect you from the network.

Proceed the Installation now?”

If you click next your internet connection temporarily goes down because Oracle installs an extra network adapter. This has no further consequences for your daily tasks.

Click Yes

Install VirtualBox
Install VirtualBox

Last warning, after you click install your internet will be temporarily disconnected.
Click Install

Install VirtualBox
Install VirtualBox

The next step installs the driver that is required for VirtualBox.
Click Install

Install VirtualBox
Install VirtualBox

Click Finish

Install VirtualBox
Install VirtualBox

VirtualBox has been installed. We can continue with the next step: Configuring VirtualBox for Windows 10.


Configuring VirtualBox for Windows 10

Now that virtualbox is installed, we can start configuring the virtual machine.

My screenshots are unfortunately in Dutch, but the principle is the same.

Click New in the upper-left corner.

Configure a virtual machine for Windows
Configure a virtual machine for Windows

Enter the desired name. For me that is Windows 10. If you are going to create multiple Virtual machines, you can use Windows 10 – Development for example.

Keep as version Other Windows (64-bit)
Click Next

Configure a virtual machine for Windows
Configure a virtual machine for Windows

The required memory for Windows 10 is at least 2024MB. Make sure you use 2024MB or more. 2024MB = 2GB

Click Next

Configure a virtual machine for Windows
Configure a virtual machine for Windows

The recommended size is 20GB. Windows 10 requires at least 16GB.
Create a new Virtual Hard Disk
Click Create

Configure a virtual machine for Windows
Configure a virtual machine for Windows

leave the default setting or use VHD.
Click Next

Configure a virtual machine for Windows
Configure a virtual machine for Windows

The difference between these 2 institutions is that Dynamic can expand itself. Allocated is a fixed size. Choose the one that suits you best.

Configure a virtual machine for Windows
Configure a virtual machine for Windows

Choose a location for your Virtual Hard Disk and choose the size. Again, the default is 20GB.
Click Create

Configure a virtual machine for Windows
Configure a virtual machine for Windows

We have completed the configuration of the virtual machine. We can now start installing Windows in VirtualBox.

Configure a virtual machine for Windows
Configure a virtual machine for Windows

Install Windows in VirtualBox

The ISO I downloaded is a beta version which was only in English. Since then I have updated the tutorial, but not the screenshots.

Change the settings as desired. I kept everything on the standard settings.
Click Next

Install Windows in VirtualBox
Install Windows in VirtualBox

Click Install now

Install Windows in VirtualBox
Install Windows in VirtualBox

Check I accept the license terms and click Next

Install Windows in VirtualBox
Install Windows in VirtualBox

We are installing a new windows so click the option Custom: Install Windows only (advanced)

Install Windows in VirtualBox
Install Windows in VirtualBox

Select the Unallocated Space drive if there are more.
Click Next

Install Windows in VirtualBox
Install Windows in VirtualBox

Click OK

Install Windows in VirtualBox
Install Windows in VirtualBox

Sit back and relax. Windows will be installed.
Click Restart now to speed it up.

Install Windows in VirtualBox
Install Windows in VirtualBox

After the restart, Windows 10 will configure itself. That can take a while.

Install Windows in VirtualBox
Install Windows in VirtualBox

Click Use express settings or Customize.
I clicked Use express settings.

Install Windows in VirtualBox
Install Windows in VirtualBox

Create an account and click Finish.

Install Windows in VirtualBox
Install Windows in VirtualBox

That is it. You should now be able to start Windows in VirtualBox. Success with it!

If you encounter erroneous steps, can you comment this below?

FIX: Bluetooth could not connect, try again later by Bas Wijdenes

Bluetooth could not connect, try again later the basics.

Everyone has their fair share of problems with Bluetooth, including me. I ran into “Bluetooth could not connect, try again later” as well. After thoroughly searching the internet I found the solution that fixed it for me. I found the steps on Microsoft but these didn’t include screenshots, so hereby also mine tutorial with screenshots.


  • Open Start in the left-bottom corner and search for Services.msc.
    Or press Windows R and type in Services.msc and click OK.

    Bluetooth could not connect, try again later
    Bluetooth could not connect, try again later
  • Sort the services by name and scroll to Bluetooth Support Service.
  • double click Bluetooth Support Service.
  • Open the Log On tab.

    Bluetooth could not connect, try again later
    Bluetooth could not connect, try again later
  • Change the selection to This account.
  • Open Browse
  • Type in Local Service and click Check Names.
  • Click OK.

    Bluetooth could not connect, try again later
    Bluetooth could not connect, try again later
  • Click OK again.

Best is now to just restart your computer. You could also try to restart the Bluetooth Support Service.

Bluetooth could not connect, try again later


Recap

There is not much more to say about Bluetooth. Everyone uses it nowadays. Bluetooth is for example in your phone, but also wireless headsets or wireless mouse use it. This also causes the above problems with your windows 10.

I am convinced that there are more solutions for this problem. The above solution has solved my problem and I therefore expect that this will be the solution for most users. If this is not the solution for you, or have you found another solution, would you like to indicate this below? Then I extend the manual.

I like to hear how I can improve my blog posts or what I have to do differently. You can give feedback below or if you want to say something else, you can of course. Positive feedback is always nice 😉.

FIX: Please set stopOnMultipleConnections to false in public settings

Azure Automation the basics

Within Azure Automation an option has been added to update your servers. You can find this under Update Management. Because there is an option to add servers that are not in Azure, this may replace WSUS servers in the future, but for now I only use it for servers within Azure.

I thoroughly tested the tool in my developer tenant, but unfortunately my developer tenant is not linked to the company SCOM environment.

I wanted to start a pilot after testing with a client with 10 servers in Azure. I expected this to go smoothly, but to my surprise I got the following error message: “Please set stopOnMultipleConnections to false in public settings”

When I tried to install the agent from the Azure Portal, I received the error message as in the screenshot below.

Please set stopOnMultipleConnections to false in public settings
Please set stopOnMultipleConnections to false in public settings

By clicking the error I got a more detailed error message:

VM has reported a failure when processing extension ‘MicrosoftMonitoringAgent’. Error message: “This machine is already connected to another Log Analytics workspace, or managed by System Center Operations Manager. Please set stopOnMultipleConnections to false in public settings or remove this property, so this machine can connect to new workspaces. Note that this machine may be billed multiple times for each workspace it report to.” 

This machine is already connected to another Log Analytics workspace, or managed by System Center Operations Manager. Please set stopOnMultipleConnections to false in public settings or remove this property, so this machine can connect to new workspaces
Don’t copy the error message. It looks ridiculously bad.

The error message was clear for me. We use SCOM to monitor the servers. I couldn’t update the monitoring agents because the SCOM agent was already installed. Although the error message was clear, I wasn’t sure how to do that. Took me awhile to figure out and that’s why I made a tutorial.


Lets fix  ‘Set stopOnMultipleConnections to false in public settings’.

Before you start with the tutorial, keep in mind what the setting does. It’s possible that the agent will communicate with two OMS workspaces and you’ll have to pay double for the VMs.

Log in to portal.azure.com and open the Microsoft Operation Management Suite (OMS).

  1. Click the gearwheel in the top-right cornor
  2. Open Connected Sources 
  3. Click Windows servers
  4. Copy the workspace ID and Primary Key
This machine is already connected to another Log Analytics workspace, or managed by System Center Operations Manager.
This machine is already connected to another Log Analytics workspace, or managed by System Center Operations Manager.

The trick here is that we’ll have to deploy the Monitoring Agent  with PowerShell.

Open PowerShell_ISE  (Control + R > Powershell_ISE)

Log on to Azure

Login-azurermaccount

Select the correct subscription

select-azurermsubscription -subscriptionid YOURSUBSCRIPTIONID

Now copy/paste the following script, but change the settings to your own settings.

  • WorkspaceId
  • WorkspaceKey
  • My location is West Europe, yours can be different.

You’ve already copied them from a previous step.

Beware! This script will install the extension for all virtual machines in your tenant.
If that’s not what your want, copy the script between the foreach loop {} and set the VM and ResourceGroupName yourself.

$vms = get-azurermvm

$PublicSettings = @{"workspaceId" = "WORKSPACEIDHERE";"stopOnMultipleConnections" = $false}

$ProtectedSettings = @{"workspaceKey" = "WORKSPACEKEYHERE"}

foreach ($vm in $vms){

write-output$vm.name

Set-AzureRmVMExtension -ExtensionName "Microsoft.EnterpriseCloud.Monitoring" `

-ResourceGroupName $vm.resourcegroupname`

-VMName $vm.name`

-Publisher "Microsoft.EnterpriseCloud.Monitoring"`

-ExtensionType "MicrosoftMonitoringAgent"`

-TypeHandlerVersion 1.0`

-Settings $PublicSettings`

-ProtectedSettings $ProtectedSettings`

-Location 'West Europe'

}
We’ll set the StopOnMultipleConnections to false in the PublicSettings.
If you run this script:
get-AzureRmVMExtension-VMName VMNAME-ResourceGroupName RESOURCEGROUPNAME -Name "Microsoft.EnterpriseCloud.Monitoring"
It will show that the settings are correct.

Recap

Even though this is probably the future, I still have a lot of problems with this tool and I think it is not mature enough yet. For example, you can’t install 2 hybrid workers on 1 server, so managing centrally from 1 Automation and OMS is a difficult problem.
I hope that these changes will be implemented, but for the time being I will stick to one customer and wait for a while.

FIX: Scheduled Task launch Failure error 2147943726

Launch Failure 2147943726 the basics.

Scheduled tasks are widely used in business among IT professionals.

I got the launch failure at a task that normally ran weekly. The scheduled task did not want to start anymore, and it seemed as if the task had gone into some loop. I continued to get the error message “Task start failed Launch Failure with Error code 2147943726”.

There are two solutions in the manual below.

The first solution is the most common with scheduled tasks.
Users create a task with their own credentials and not with a service account. When you create the task, you enter your password once and it is cached. So if the user changes his password, the scheduled task’s password will no longer be correct.

The second solution is more a work around for this problem.
The task can go into a kind of loop which makes it seem like it is running all the time in the background. If you do the adjustment in the manual, the task will stop the wrong run and it will run again.

After the blog post I tell a little bit about Azure Automation, but I will not go into this too deeply. If you are a system administrator, it may be interesting for you to use Azure Automation. In any case, I try to use it as much as possible in my daily work.


Tutorial 1 – Reset the user credentials used to create the task.

One of the common reasons your tasks failed is because the username/password that’s was being used after the task creation probably changed or have an outdated password.

  1. Right click your Task.
  2. Go to Properties.
  3. Select the general tab.
  4. Click Change User or Group..
  5. Enter the username you want the task to use.
  6. Give in your credentials.

Verify everything works by running the task.


Tutorial 2 – Stop the existing instance.

  1. Right click the Task that’s failing.
  2. Click Properties.
  3. Go to the Settings tab.
  4. Below in the Settings tab is a drop-down menu open that.
  5. Choose Stop the existing instance.
    Task start failed launch Failure error 2147943726
    Task start failed launch Failure error 2147943726

    Your task should run again now.


Azure Automation over Scheduled tasks.

Scheduled tasks are still widely used. Nowadays as a system administrator I prefer to use Azure Automation , with Azure Automation you’ll be able to scheduled task with more ease than Scheduled tasks.

I won’t be going to deep into it, but with Azure Automation you can add credentials, hybrid workers, etc. and you’ll have all your scripts run from one central point in your environment. You can also easily run scripts against Office 365 or Azure itself. Setting up Azure Automation is done in an hour. I’ve even started writing blog posts about issues I found while playing around with it.

FIX: Account is not authorized for remote login by Bas Wijdenes

The connection was denied because the user account is not authorized for remote login.

First of all, I want to mention that I received this message within Azure AD DS, but that the manual is generic and can also help you if you encounter this error message. The point is that you cannot log in with a domain account on a device that is also domain joined.

After my previous post about an error message within Azure Active Directory Domain Services I ran into a problem again. It is always nice when you encounter small problems in a developer environment, so you can avoid them in production…

Normally as a domain admin you should not run into this problem on servers that are added to the domain, but apparently if you add a server to Azure AD DS.

As described above, this may well be the case for notebooks or other devices.

The error message:

The connection was denied because the user account is not authorized for remote login.
The connection was denied because the user account is not authorized for remote login.

Let’s fix “The Connection was denied because the user account is not authorized for remote login.

The manual is divided into a short and long guide. The short guide is for system administrators and if you do not have experience with troubleshooting you can better follow the long guide.

short guide
  1. Press Control + R
  2. Type in lusrmgr.msc
  3. Go to Groups and open Administrators
  4. Add new user and search in your Azure AD Domain Services
  5. Login with administrator credentials in Azure AD Domain Services
  6. Add the administrator or group to administrators.

long guide

Below is a longer tutorial for those who don’t understand the short guide.

Right click start > Run, or press Control + R.
You can also search for lusrmgr.msc in start.
Below I used CTRL + R.

The Connection was denied because the user account is not authorized for remote login
Search for lusrmgr.msc

Go to Groups and double-click Administrator.

The Connection was denied because the user account is not authorized for remote login.
Open groups and double-click Administrators

Click Add…

If the server is correctly domain-joined in Azure AD Domain Services then you should be able to search directly in the domain, you will only have to enter the administrator credentials of your Azure AD Domain.

The Connection was denied because the user account is not authorized for remote login.
Add domain user

You should be able to log on your Azure AD Domain joined server with your domain admin account.

How to join VM to Azure AD DS by Bas Wijdenes

Joining Azure AD DS throws an incorrect password

Azure Active Directory Domain Services is a new product within Microsoft Azure. The product is still fairly new and I find it in general not yet mature enough to actively use. The idea behind Azure AD DS is that you no longer need to use a domain controller within your domain. This has the advantage that you have little to no maintenance in your domain.

The disadvantage is that you miss many functions. For example, I tried to create an Exchange hybrid environment within Azure AD DS, but unfortunately this is not possible because you can no longer manage groups such as Schema admins, or Enterprise admins.

I have deployed Azure AD Domain services in my developer tenant. I then tried to connect a Server, only I got the error message that my “User name or password is incorrect“. Strange because those are the same login details that I used to create the environment.

“the user name or password is incorrect”

“The following error occured attempting to join the domain” “The user name or password is incorrect”
“The following error occured attempting to join the domain” “The user name or password is incorrect”

Fix: Joining Azure AD DS throws an incorrect password

Microsoft gives as best practice that you must log in with the UserPrincipalName format.

“We recommend using the UPN format to specify credentials.

If a user’s UPN prefix is overly long (for example, joehasareallylongname), the SAMAccountName might be auto-generated. If multiple users have the same UPN prefix (for example, bob) in your Azure AD tenant, their SAMAccountName format might be auto-generated by the service. In these cases, the UPN format can be used reliably to log on to the domain.”

To keep the tutorial as short as possible, do not use the UserPrincipalName format 😉. You can log in with the legacy login with DOMAIN\Username format, even for an Azure AD DS environment only.

My UserPrincipalName in my developer tenant is:

Adm_wijdenes@Baswijdenesoutlook026.onmicrosoft.com

And now to let the Server join the domain I used:

Baswijdenesoutlook026.onmicrosoft.com\Adm_wijdenes

and then it worked!


Recap

Do you have any additions to:

“The following error occured attempting to join the domain”

“The user name or password is incorrect”

While adding a device in Azure Active Directory Domain Services, do you want to add other additions or feedback about this post? Then you can leave a comment below.

FIX: WslRegisterDistribution failed with error: 0x80070057 Kali

WslRegisterDistribution failed with error: 0x80070057 the basics.

I tried to start Kali Linux on my Windows PC, but unfortunately, I got the following error message:

Installing, this may take a few minutes…
WslRegisterDistribution failed with error: 0x80070057
Error: 0x80070057 The parameter is incorrect.

I myself completely removed the Kali Linux installation and then reinstalled Kali Linux from the Microsoft Store. Unfortunately, all my settings were removed.

So, I started Googling to search for other solutions for other Kali Linux users on Windows so that they wouldn’t run into the same problem.

Because I already re-installed Kali Linux I tested all 3 options.

In the tutorial below there are 3 options for restoring your Kali Linux.

  1. Option 1 is a workaround if you want to keep the self-configured settings.
  2. Option 2 solves the problem completely, but then you have a chance that certain settings have been changed to default.
  3. Option 3 is last resort solution and will temporarily remove the entire installation.

I assume that if you use Kali Linux on Windows, you have some technical knowledge so, I haven’t added screenshots etc. everywhere. If something is not clear yet, let me know in the comments.

WslRegisterDistribution failed with error: 0x80070057 Kali
WslRegisterDistribution failed with error: 0x80070057 Kali Linux

Option 1 – The Workaround for WslRegisterDistribution failed with error: 0x80070057

Go to start and search for Command Prompt.
Or press CTRL + R and type in cmd.

Type or copy each line separately:

wslconfig.exe /setdefault kali-rolling
bash
cd

From now on you can start (as a work around) Kali Linux from Command prompt. This is of course not desirable, but it can be a temporary solution.

You will no longer receive the error message “WslRegisterDistribution failed”


Option 2 – A solution to “WslRegisterDistribution failed

Go to the following location:
You cannot copy the directory because Kali Linux is installed in a directory with random characters.

“C:\Users\%username%\AppData\Local\Packages\KaliLinux<randomchars>\LocalState\rootfs.”

Copy the rootfs folder to a different folder.
I have a “C:\temp\” folder where I copy these type of things to.By restarting Kali Linux the directory will be re-created.
After you launch Kali Linux it will start to install again. Wait until the Install is finished.
Delete the newly installed rootfs and move the old one back.
You can now use Kali Linux with most unchanged.


Option 3 – A complete fix, but not a desired one..

Microsoft Store as the last solution.

Keep in mind that all settings are removed and that you start again with a fresh installation.

  1. Search in Start for Kali Linux
  2. Right click on Kali and choose Uninstall
  3. After the uninstall, you can reinstall Kali from the Microsoft Store.

Recap

So, these are 3 options to solve your problem. If you find another solution, could you indicate it in the comments below? I’ll add it to the post.

Do you have other feedback, or do you see something that is not right? Please leave a comment!

FIX: MSVCR71.dll is missing or not found by Bas Wijdenes

Program can’t start because it is missing MSVCR71.dll the basics.

For if you’re a sysadmin, Adam the Automator created a great function to use as well.

Programs often use certain .DLL files. These files can get corrupted and your program can be unresponsive. By repairing or even replacing the .DLL you can fix the problem.

The tutorial below is not only for MSVCR71.DLL, but can be used for other .DLL files as well.  Below is a short guide only this time since it’s only a few commands you’ll have to run on your device. The screenshots of CMD will help you further. If you got here due to a different .DLL file, make sure to change the file-name in the tutorial.

Goodluck!

Short guide – Program can’t start because it is missing MSVCR71.dll

  1. Open the Explorer.
  2. Go to C:\Windows\System32 (you can also copy/paste this).
  3. Search for MSVCR71.DLL and make a copy.
    You can either search function and type in MSVCR71.DLL or alternatively write the first few letters and it will find the MSVCR71.DLL automatically.
  4. Open Start and search for CMD, right click CMD and click Run as administrator.
  5. Type in: Regsvr32.exe msvcr71.dll (you can also copy/paste this).
  6. Press Enter.
Program can't start because it is missing MSVCR71.dll
Program can’t start because it is missing MSVCR71.dll

If the MSVCR71.DLL is not there, download it from the internet and place it in C:\Windows\System32.

If that didn’t solve your problem, last resort is to scan your system with System File Checker (SFC).

SFC is used to detect and fix problems with your system. This will run a check on corrupt files and replace these.

  1. Open Start and search for CMD, right click CMD and click Run as administrator.
  2. Type: sfc /scannow (You can also copy paste)
  3. Press Enter.
Program can't start because it is missing MSVCR71.dll
Program can’t start because it is missing MSVCR71.dll

The scan will take awhile. Wait it out and test it again.