Fix Remote Desktop: Your credentials ...

What is TrayApp Error 1706? A TrayApp Error 1706 is not something you want to see. It is generally caused by an error in hexadecimal formatting, which is a common format employed by software programmers for Windows OS-compatible hardware drivers, Windows system files, and software apps. Developers and manufacturers of hardware drivers and software apps employ different codes in order to indicate different types of errors. The TrayApp error 1706 occurs in a long numeric code with a technical explanation of the cause. In many cases, the TrayApp error 1706 can have different TrayApp error 1706 parameters. It will usually sport a message like:

• Install Error 1706 Trayapp
• Reinstall Error 1706 Trayapp
• Error 1706 Trayapp crash
• Error 1706 Trayapp is missing
• Remove Error 1706 Trayapp
• Download Error 1706 Trayapp
• Error 1706 Trayapp virus

Solution

Error Causes

More often than not, the TrayApp error will occur because there are damaged files in your operating system. When the Windows system file entry gets corrupt, it means that there malfunctioning in your system and it can be exposed to major security threats. And if it’s not resolved, it can potentially result in complete and permanent data loss and can make your storage media or your system as a whole inoperable. There can be other triggers for the TrayApp error, the common of which include:

• Incomplete installation of software
• Incomplete un-installation of software
• Improper deleting of hardware drivers
• Improper deleting of software applications

If you have the TrayApp error, you realize how common it is when restarting your system followed an improper shutdown or a recent malware or virus recovery. These situations result in corruption or deletion of essential system files. When Windows system files get corrupted or go missing, the data that is needed to run software won’t be linked properly.

Further Information and Manual Repair

There are two common manual ways of fixing TrayApp error 1706. The manual solution is:

Boot Your System and Log in As Administrator.

• Click on Start and select All Programs.
• Go to Accessories, then System Tools, and select System Restore.
• In the dialog box, select, ‘Restore computer to an earlier date’ and then click on Next.

Click next twice on the dialog boxes and then the Automatic System Restore will start and restart your device.

Reimage Plus Fix for Trayapp Error 1706

This is the easiest way to resolve TrayApp Error 1706. However, there are cases when the manual process may not really work, and this can be caused by improper maintenance of your system. For that, Restoro is your short and comprehensive answer. Restoro is a multi-functional PC Fixer that works as an antivirus, registry cleaner, system optimizer, and much more. It can not only help resolve TrayApp Error 1706, but can also resolve other errors that can hinder the performance of your system, programs, and applications. It can also clean your registry and optimize your system to make it faster and quick loading. The software is compatible with all Windows versions. Just click here and download Restoro and get rid of any issues in your system!

Sticky Notes is one of the useful programs and in the early days, the option is available for users to change the font size of the text a lot easier. However, for some unknown reason, Microsoft decided to get rid of this feature in the latest Windows Update. One would expect that the feature will be replaced by an even more useful feature but it’s not which makes the Sticky Notes app worse than before. Worry not though for it doesn’t have to stay that way as there is another thing you can try to change the font size in your Sticky Notes app and that’s what we’re going to cover in this post. As mentioned, Microsoft removing this font feature is quite strange and in the past, users asked for this feature and since it’s no longer available, you can try following the steps given below to bring it back. And for that, you need to go to the Ease of Access section in the Settings app. Refer to the steps given below for more instructions. Step 1: First, tap the Win + I keys to open Settings and then go to the Ease of Access section. Step 2: After going to the Ease of Access menu and select Display from the list of options. Step 3: From there, you should see an option that says “Make text bigger”. And then use your mouse to navigate to the slider to change the size of the font. Note: Take note that after doing all the steps above, it will change not just the Sticky Notes app but also everything in Windows 10. This method is actually the best since it only changes the size of the apps rather than a wholesale change in your Windows 10 computer. Step 4: Next, scroll under Display until you see the “Change the size of apps and text on the main display” option where you’ll see that the option is 100% but you’ll want to change that to 125%. Step 5: After that, click on the drop-down menu and select 125% and then restart your Windows 10 computer. Step 6: Now open the Sticky Notes app and check if you can now change the font size in the Sticky Notes app.

As you know, Windows PowerShell is a useful command-line utility in Windows 10 that can be used to manage the Local Users and Groups which affirms the multiuser operating system principle of Windows 10. Although there are other GUI-based utilities used to manage the Local Users and Groups, there are some system administrators that would still like to use the command-line utility to manage these Local Users and Groups. So in this post, you will be guided on how exactly you can manage the Local Users and Groups using PowerShell on your Windows 10 computer. To get started, refer to the options provided below to manage both the Local Users and Groups using Windows PowerShell.

Option 1 – Manage the Local Users via Windows PowerShell

• You need to first open Windows PowerShell as an admin. To do that, just tap the Win + X keys and select the Windows PowerShell (Admin) option.
• After opening PowerShell, you need to execute the “Get-LocalUser” cmdlet so that you can find all the details about all the local user accounts in your computer which would include the Account Name, Enabled status, as well as description.

Note: On the other hand, you can also get the customized data about several objects that are related to your account. For instance, if you want to check when was the last time the Local account’s password was set, then you need to execute the “Get-LocalUser -Name root | Select-Object PasswordLastSet” cmdlet. Thus, the structure for this cmdlet is “Get-LocalUser -Name root | Select-Object *”. Here are the objects you can use to get different sorts of data:

• AccountExpires
• Description
• Enabled : True
• FullName
• PasswordChangeableDate
• PasswordExpires
• UserMayChangePassword
• PasswordRequired
• PasswordLastSet
• LastLogon
• Name
• SID
• PrincipalSource
• ObjectClass

Option 2 – Manage the Local User Groups using Windows PowerShell

• Like what you did earlier, open Windows PowerShell as admin and then execute the “Get-LocalGroup” cmdlet so you can get all the information about all the groups of all the local user accounts.
• Now if you want to create a new Local User Group, just execute the “New-LocalGroup -Name <NAME OF THE GROUP> -Description '<ENTER THE DESCRIPTION OF THE GROUP HERE>'” cmdlet.
• And if you want to add Local User Accounts to a specific group, just execute the “Add-LocalGroupMember -Group '<NAME OF THE GROUP' -Member ('NAME 1','NAME 2','<ROLE>') -Verbose” cmdlet. You could also use the “Get-Localuser -Name john | Add-LocalGroupMember -Group '<NAME OF THE GROUP>'” cmdlet for the same purpose.
• If you want to display all the User Accounts of a specific group, just use the “Get-LocalGroupMember –Group ‘ ’” cmdlet.
• Now if you want to remove a local user account from a group, all you have to do is use the “Remove-LocalGroupMember -Group '<NAME OF THE GROUP>' –Member <NAME OF THE LOCAL USER ACCOUNT>” cmdlet.

When you have to connect to a drive that’s on a different computer or on external storage, that’s where the mapped network drives come in. Mapped network drives make accessing files a lot easier. However, there are times when it won’t work for some reason. Windows will notify you about the unavailability of mapped network drives in several ways. For one, Windows might display a red X on the network drives or it could be that its status will be unavailable when you try to use it from the Command Prompt or via a notification. It is recommended that you run a few scripts when you log in to your PC as it may so happen that the network drive takes more than usual to connect. Before you start troubleshooting the problem using the given options below, keep in mind that some workouts might only work under certain scenarios. You might need some network access at logon or you might need access to the Group Policy settings. So you need to choose what you prefer more. You can try the given workarounds below if the mapped network drives are not showing or connecting or working on your Windows 10 computer. These workarounds use scripts to make sure that you are connected to them as soon as you start to use your PC. As mentioned, before you can troubleshoot, you need to create scripts first. There are two scripts here namely MapDrives.ps1 which is executed by the second script named MapDrives.cmd and is done at a regular and non-elevated Command Prompt. Follow the steps below to get started.

• You have to create a script file named “MapDrives.cmd” first and then save it on a place where the files are safe. To do that, open a text editor like Notepad and then copy and paste the following script:

PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%StartupLog.txt" 2>&1 PowerShell -File "%SystemDrive%ScriptsMapDrives.ps1" >> "%TEMP%StartupLog.txt" 2>&1

• After that, save the file and name it “MapDrives.cmd”.
• Next, create a script file named “MapDrives.ps1” and then copy and paste the following content. Just make sure to save both scripts in the same folder.

$i=3 while($True){     $error.clear()     $MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath     foreach( $MappedDrive in $MappedDrives)     {         try {             New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True         } catch {             Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath"         }     }     $i = $i - 1     if($error.Count -eq 0 -Or $i -eq 0) {break}     Start-Sleep -Seconds 30 } Note: Now that you’ve created the script files, it’s time for you to proceed to the options given below.

Option 1 – Try creating a startup item

Note that this option only works on devices that have network access at login. So if it’s not there, the script will fail to reconnect the network drivers automatically. To create a startup item, here’s what you have to do:

• Open the Startup folder located at %ProgramData%MicrosoftWindowsStart MenuProgramsStartUp.
• From there, copy and paste the MapDrives.cmd.
• After that, open the Scripts folder located at %SystemDrive%Scripts copy-paste MapDrives.ps1 and then copy and paste MapDrives.ps1 in there.

Note: After you complete the steps above, a log file named “StartupLog.txt” will be created in the %TEMP% folder. Now all that’s left for you to do is to log out of your computer and then log back in. This will ensure that the mapped drives are open.

Option 2 – Create a scheduled task

It is possible to create a scheduled task that runs as soon as you log in to your computer. To create a scheduled task, follow the steps below.

• You have to copy the MapDrives.ps1 script file to the scripts folder of Windows located at %SystemDrive%Scripts.
• After that, open the Task Scheduler and select Action > Create Task.
• Next, type a name and description of the task in the General tab.
• Then click on the Change User or Group button and select a local user group and click OK.
• Now check the box labeled “Run with highest privileges” and switch to the Triggers tab.
• From there, create a new trigger with the “At Logon” option in the Begin the task drop-down menu and then click OK.
• After that, switch to the Actions tab and create a new action then choose to Start a program.
• Next, type “Powershell.exe” in the Program/Script field, and in the Add arguments (optional) field, type the following:

-windowsstyle hidden -command .MapDrives.ps1 >> %TEMP%StartupLog.txt 2>&1

• And in the Start in the (optional) field, type “%SystemDrive%Scripts” as the location of the script file.
• Now under the Conditions tab, select the “Start only if the following network connection is available” option and then select Any connection and click OK.
• Restart your computer or log off from your account and then log back in so that the task will be executed.

Option 3 – Use the Group Policy settings

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

What Is STOP 0x00000014 Error?

0x00000014 error is actually an error that is always displayed on a STOP message.

It is also known as Blue Screen of Death, abbreviated as BSOD. When this error occurs, the message that is displayed to the user either says ‘STOP: 0x00000014’ or states ‘CREATE_DELETE_LOCK_NOT_LOCKED’. It is crucial to fix this error to ensure your program is functioning appropriately. If this error message is not rectified, you might be opened to other error messages, such as error code 0x000000d1. 

Solution

Error Causes

As far as the causes of STOP 0x00000014 error are concerned, this error usually occurs when a device driver or hardware problem occurs. This error may also occur if users attempt to run some specific application or update or modify an existing application. When a 0x00000014 error occurs, the operating system restarts to disable the PC from performing any further.

Without taking into consideration the causes of its occurrence, it is crucial to make sure that the 0x00000014 error is fixed as soon as possible to eliminate any undesired inconvenience in the future.

Further Information and Manual Repair

A lot of times when an operating system tries to recover from the STOP 0x00000014 error, the user is prompted that Windows has recovered from an unexpected shutdown.

However, if Windows fails to recover on its own, manual repair has to be performed.

While there are several ways this error can be fixed, some of the most effective and efficient ways of troubleshooting the 0x00000014 error are listed below as follows.

• Restart your computer. Often simply restarting the computer can help eliminate the problem.
• If restarting the system doesn’t help, find if you have recently modified or altered any hardware or driver. It is possible that the 0x00000014 error has been caused by the recent modification. Undo the changes and find out if the error occurs again. If it doesn’t, it is highly likely the issue has been resolved.

However, if the error persists, some solutions that may work are outlined below.

• Start your system using the Last Known Good Configuration. This will undo any changes in the driver and recent registry.
• Another solution is to manually perform System Restore. This will also return the system back to its former state.
• Another idea that my work is to use roll back the device driver. When the driver will return to its previous version, the problem will easily be resolved.

To keep the 0x00000014 error from occurring in the future, it is advised to unplug any newly installed hardware or reinstall any deleted software.

If you're not tech-savvy and wish to get this error code rectified in a jiffy, download a powerful automated tool and perform a computer scan.

• In your Graphics Settings, select r5apex.exe and change the Graphics performance preference to Classic App, set it to High Performance, and then launch the game as an administrator when you want to play.
• Inside the Nvidia Control Panel, click “Manage 3D Settings”, and select Apex Legends and change it to “Prefer Maximum Power”
• You can also change “pre-rendered frames” to 1, but it will make you lag just a tiny, tiny bit.
• Turning the shader cache on can help improve FPS, but on some systems, it may cause additional negative performance changes.
• If you have the ability to use G-Sync, use that as well (Only available on some monitors and graphics cards)
• From the task manager, change the priority of r5apex.exe to “High” and close out of other applications.
• Update your graphics drivers.
• Ensure your PC complies with the games minimum system requirements:
  • OS: 64-bit Windows 10
  • CPU: Intel Core i3-6300 3.8GHz / AMD FX-4350 4.2 GHz Quad-Core Processor
  • RAM: 6GB
  • GPU: NVIDIA GeForce GT 640 / Radeon HD 7700
  • GPU RAM: 1 GB
  • HARD DRIVE: Minimum 30 GB of free space
• Check to see if your system has the game’s recommended hardware requirements:
  • OS: 64-bit Windows 10
  • CPU: Intel i5 3570K or equivalent
  • RAM: 8GB
  • GPU: Nvidia GeForce GTX 970 / AMD Radeon R9 290
  • GPU RAM: 8GB
  • HARD DRIVE: Minimum 30 GB of free space
• Within the game, try to set the settings to:
  • Full Screen
  • Disable V-Sync
  • Anti-Aliasing to Disabled/TSAA (slight performance difference)
  • Use Native Resolution
  • Keep Field of View at around 80-100
  • Texture Streaming Budget to High
  • Texture filtering as low as possible while still being playable
  • Ambient occlusion as low as possible
  • Shadow all to Low / Lowest
  • Model detail low
  • Effects detail low
  • Volumetric lighting / Dynamic spot shadows Disabled
  • Ragdolls low
  • Impact marks the lowest
• Make sure other applications are not placing overlays (Discord, GeForce, Xbox Gaming)
• Clean your temporary files and uninstall other games to give your PC room to have the game run.
• Don’t use products like CCleaner as they may remove necessary files from your computer.
• Closeout of Chrome when you’re playing the game or follow our guide on Optimizing Chrome Performance

If you got an error message saying, The INF file you selected does not support this method of installation while trying to install a driver using the “Install” option in the right-click context menu, read on as this post will guide you in fixing the problem. The INF file mentioned in the error message is a text file that’s divided into different types of formatted sections. Each one of the sections is designed for a particular purpose. For instance, one section is designed to copy files or to add entries to the registry. INF files are used to install drivers. However, if something is wrong, you might encounter this error while installing a driver on your Windows 10 computer. To resolve this problem, you can try to download the driver again from the official manufacturer website or check if the driver is compatible with your computer’s operating system architecture or you can also try installing the driver from the Device Manager. For more details, follow the given options below.

Option 1 – Try downloading the driver again from the official website of the manufacturer

Usually, you shouldn’t encounter this kind of issue no matter what installation method you used on your Windows 10 PC. However, there are times when the driver itself is corrupted for some reason which is why you are unable to complete the installation and receive an error message instead.

Option 2 – Try checking if the driver is compatible with the OS architecture

It is possible that you’re getting this error if you have a driver that is compatible with a 32-bit system and you are trying to install it on a 64-bit system and vice versa. Thus, you need to check if the driver you are trying to install is compatible with your operating system if you haven’t done it when you’ve downloaded the driver from the website of the manufacturer. To check the system architecture, in the Start Search, type “msinfo32” in the field and hit Enter to open the System Information window. From there, you should see all the information about your operating system. In addition, you can also search “system information” in the Cortana search box and look for the System Type entry and open it.

Option 3 – Try installing the driver from the Device Manager

If you have the driver files on your PC and you have to update a driver, refer to the steps given below to be guided on how to install the driver from the Device Manager.

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the driver you want to update, and then right-click on each one of them and select the Update Driver from the menu.
• After that, click on the “Browse my computer for driver software” option.
• Next, select the “Let me pick from a list of available drivers on my computer” option and then click the Next button.
• On the next screen, you should see the “Have Disk” option. Click on this option and then click on the Browse button to go to the location of the file. After that, you shouldn’t have any problem installing the INF file.

Option 4 – Try running the System File Checker Scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the “The INF file you selected does not support this method of installation” error. 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

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.

 Now restart your computer.

If you are tried encrypting or decrypting a file using the default EFS engine but you receive an error message instead saying, “Error Applying Attributes, An error occurred applying attributes to the file: The specified file could not be decrypted”, read on as this post will help you sort out the problem. If you encounter this error you can use the error code in it. You will most likely get error code 0x80071771. This kind of error occurs when the File Explorer’s copy and paste feature was not able to read the source file being encrypted or decrypted. It could also occur if you try to access a file that has been on another computer previously.

To fix error code 0x80071771 when decrypting or encrypting a file, refer to the instructions provided below.

Step 1: You need to check first if you can decrypt the files encrypted by EFS. However, if you can’t, just proceed and then take full control of the file. Step 2: To take control of the file, open File Explorer and right-click on the partition, and then click on Properties. Step 3: After that, click on the Edit button under the Security tab. Step 4: Next, make sure that “Everyone” is selected under the Group or user names section. Step 5: Afterwards, the Permissions for Everyone section will be activated. Just make sure that all the checkboxes for Allow are checked and then click on the Apply button. Step 6: Once you’re done, click on the Advanced button. This will open a new window labeled Advanced Security Settings. From there, click on the Change link under the Owner section. Step 7: Now type your account name in the field and click on Check Names to verify the account name and click OK. Step 8: After that, select the “Replace owner on sub-containers and objects” option and then click OK. Step 9: Next, select Administrators in the Group or User names list and select Full Control in the Permissions for Administrators panel and click OK.

Error Code 3 - What is it?

Error code 3 is a type of PC windows error that can occur on any Windows version including Windows XP, Vista, Windows 7, or 8. This error code means that the system cannot find the path specified. The error 3 messages are displayed in the following format: “Error_ Path_Not_Found” or it may sometimes be displayed with the value 3 in this format:  (0x80070003: Error_Path_Not_Found)

Solution

Error Causes

The error code 3 indicates poor PC maintenance. It is a critical sign of an unstable system. The causes of this error code are:

• Missing or broken system files
• Registry issues

This error code poses serious system threats and should be resolved immediately before the damage is done. If you don’t address this error timely, your PC may be exposed to risks like system failure and crash. And this may lead to valuable data loss.

Further Information and Manual Repair

To resolve this error on your system, you don’t have to hire a technician or be technically sound yourself. What you simply need to do is clean the registry. Here are 2 ways to clean the registry:

1. Manually by Launching Registry Editor

First, launch the Windows registry editor by clicking the start button and selecting run. In the text box type, 'Regedit' and press enter and click OK. Before you make changes to the registry, make sure you create a backup of your existing registry. This is advisable because if you accidentally lose important data during the cleaning process you can also recover the lost data. Once you create a backup, now get started with the cleaning process. Expand HKEY_CURRENT_USER" key, then click on the software key and look for applications that you think could have corrupted the registry. Now delete them. After that, remove the unwanted start-up items, by accessing this link:  My Computer HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows Current Version. Now click on the run tab and delete invalid entries/ values. This process may be time-consuming and for some, it may be slightly technical to identify unwanted start-up items.

2. Download Restoro Registry Cleaner

Another way to clean and repair the registry is to download Restoro. This is an innovative and a highly-functional registry cleaner. It is embedded with an intuitive algorithm that detects all the registry issues instantly and removes them right away in just a few simple clicks. It removes all the unnecessary and obsolete files, repairs the registry, and fixes the damaged dll and system files. It has a user-friendly interface and simple navigation which makes it easy for all levels of users to work around it. This software is compatible with all Windows versions. Besides functioning as a registry cleaner, Restoro also functions as an antivirus and a system optimizer. It scans and removes all kinds of malicious software and simultaneously boosts the speed of your PC. Click here to download Restoro and resolve error 3 “Entry_Path_Not_Found” on your PC now!

Error Code 0x800ccc13– What is it?

0x800ccc13 is an error message related to sending email using Outlook. Many people are receiving this error after making an upgrade from Windows 7 or Windows 8.1 to Windows 10. The error message appears when you try to send an email message with the use of a POP3 account or an IMAP account in an Outlook profile that has an Exchange Server 2010 mailbox configured. A common complaint would be: Since upgrading to Windows 10 I cannot send email from Outlook 2013. Mail stays in the Outbox, and I get: Error 0x800CCC13. Cannot connect to the network.

Symptoms

This problem may arise under the following situations:

• You are using Microsoft Office Outlook in online mode to connect to a Microsoft Exchange Server 2010 mailbox
• When you add an additional POP3 or IMAP account in the same Microsoft Outlook profile
• You are sending an attachment through email.
• You try sending an email by selecting POP3 or IMAP account as the sender

During these circumstances, the email message stays in the Outbox and you receive the following error message: Task '<the POP3 account or the IMAP account> - Sending' reported error (0x800CCC13): 'Unable to connect to the network. Check your network connection or modem.'

Solution

Error Causes

Error Code 0x800ccc13 occurs because the system files in Windows 10 during the upgrade became corrupted and most likely caused authentication issues. It can happen with any version of Outlook. Damaged data files will also cause error code 0x800ccc13 to manifest. Overall, the corruption of the Microsoft Windows System could be a result of an installation partially done (or an incomplete one), deletion of any application or hardware erroneously, and or malware or adware infestation.

Further Information and Manual Repair

Method 1:

Use the Windows System File Checker to repair corrupted files Verify that your SMTP, username, and password settings are correct. Now, in order to correct missing or corrupt Windows System files, try the following solution by running a command. This is known as the System File Checker. Follow the steps below to invoke the program using a command prompt command:

1. At first, you need to open the command prompt. To do so, right-click the Windows button in the bottom left of the screen, and select Command Prompt (Admin).
2. Now, enter the following command

sfc/scannow

When it is done, a message will confirm that Windows found some corrupt or missing files and it has successfully repaired those. Check the Outlook and see if your emails are sending. If the problem persists, don’t worry there is another way to solve this. Users have found another command helpful is using the NetShell utility from the command prompt, which is similar to the above solution.

1. Open the Command prompt by Right-clicking the Windows button in the bottom left of the screen and select Command Prompt (Admin).
2. Enter the following command

netshwinsosk reset

This helpful command will reset the network adapter to its default settings. Hope this will solve your problem. If not, you may want to try the Method 2 listed below.

Method 2:

For this method, you need to consider the following things:

• Are you using POP3, IMAP, or Exchange server for your email account?
• How many email accounts have you configured in your Outlook?
• Is there an undelivered email stuck in your Outbox?
• If you are trying to send an attachment, what is the size of the attachment?

Try the following:

1. Move or delete any undelivered email that is stuck in the Outbox folder, and then try sending an email and verify the result
2. Start Outlook in Safe Mode by following the instructions below

Hold down Windows key + R. Copy this command Outlook /safe Note, there is a space between Outlook and / Paste it in the open box and press Enter If Outlook in Safe Mode works, disable the add-ins by following the steps below and determine if the problem is caused by add-ins.

• Click File menu, click Options, Add-ins, Go button beside Manage Com-in Add.
• If there are add-ins listed, clear the checkbox.
• Close Microsoft Office and restart it.
• Disable the add-ins one at a time. Now, restart Outlook and repeat the procedure once more. If the problem appears again, it will help you find which add-in is causing the problem.

3. Start the computer using the clean boot. Now, try to send an email and see the result.
4. If the problem still lingers, create a new profile and configure the email account.

If you do not possess the technical expertise required to accomplish this yourself or do not feel comfortable doing so, download and install a powerful automated tool to get the job done.