Fix DISM Error: The scratch directory size ...

Uncdms.dll Error Code - What is it?

Uncdms.dll is a Dynamic Link Library file and a crucial part of the Windows Desktop Search Software. It is used to search emails, documents, photos, videos, and folders instantly. However, the Uncdms.dll error pops on the screen, when the Windows Desktop Search Software fails to start. The error message is displayed in one of the following formats:

• “Uncdms.dll cannot be found.”
• “Windowssearch.exe – cannot find the component. This application has failed to start because uncdms.dll was not found. Reinstalling the application may fix the problem.”
• “The file uncdms.dll is missing.”

Solution

Error Causes

Uncdms.dll error code may pop on your screen due to multiple reasons. These usually include but are not limited to:

• Viral infection
• Issues with Windows Desktop Search
• Registry corruption
• Uncdms.dll accidentally deleted during program un-installation

Further Information and Manual Repair

If you experience an Uncdms.dll error code on your system, fix it right away. This error is easy to resolve. You don’t have to be technically sound to resolve the uncdms.dll error code. Try the methods listed below to resolve without any hassle:

Method 1 - Check Your Recycle Bin and Restore the Deleted Uncdms.dll File

Since DLL files are shared files, there is a possibility that you accidentally deleted them while uninstalling some other program. To fix the issue, simply go to the recycle bin and look for the file. If you locate it, reinstall it. If you can’t, then it is advisable to download the Uncdms.dll file from a trusted DLL file website.

Method 2 - Uninstall and Then Re-install Windows Desktop Search

If the error code is related to issues with the Window Desktop Search application, then simply uninstall this software and re-install to resolve. To do this, click the start button, go to the control panel and then add/ remove programs. Now choose Windows Desktop Search from the list of programs and click Remove. After that, reboot your PC to activate changes. Now download the software and follow the same process and reinstall the Windows Desktop Search program on your PC. To activate changes, reboot. This will hopefully resolve the issue.

Method 3 - Update Windows

As this file is included in the service pack, try updating the Windows Utility to resolve the Uncdms.dll error code. To get started, click start and then go to the control panel, now choose Windows update. Follow the instructions to install Active X and then click install to update Windows Utility. Restart your system to bring the changes into effect.

Method 4 - Scan for Viruses and Repair the Registry

Whether the underlying cause of the Uncdms.dll error code is viral infection or registry corruption, it is advisable to download Restoro. It is an advanced and multi-functional PC Repair Tool integrated with 6 powerful utilities including antivirus and a registry cleaner. It scans and removes all types of viruses. The registry cleaning utility works simultaneously and removes all the unnecessary files corrupting the registry including cookies, temporary files, internet history, and junk files, and repairs it in seconds, thereby resolving the Uncdms.dll error immediately. Click here to download Restoro - PC Fixer

If you got encounter an error message saying, “Error opening file for writing” while running a setup file to install some program on your computer, read on as this post will give you some suggestions on how you can fix it. You can encounter this error when running a setup file for installing a program like GlassWire, Notepad++, VLC, Steam, OBS, Mod Organizer, WinpCap, NSIS, FileZilla, BSPlayer, Kodi, Wireshark, rtcore64, qt5core.dll, MSI Afterburner, GWCtlSrv.exe, npf.sys, vcredist_86 and many more. And so when this error pops up while you run a setup file, refer to the steps given below which might help resolve the problem. Step 1: First, you have to make sure that there is no other installation in progress as multiple installations can most likely cause this error to show up. You can restart your computer and try to run the setup file again. Step 2: If you still got the error even after your restart your computer, click on Retry to try again and if it does nothing, click Abort to terminate the installation. After that, go to the folder where you’ve placed the setup file and then delete it. Step 3: Make sure that you have enough disk space on your computer. You can use the Windows 10 Storage Sense feature which can clean all the temporary files from your computer and help you save storage space. To use Storage Sense, follow the steps below.

• Open Setting > System > Storage from the WinX Menu.
• From there, you will see a list of all the local and connected storage devices along with the details on the free space.
• Now make sure that the Storage Sense feature is turned On then go find a link that says “Free Up Space” and click it to open.
• After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
• Windows Upgrade Log Files
• The system created Windows Error Reporting Files
• Thumbnails
• Temporary Internet Files
• Previous Windows Installation Files
• Delivery Optimisation Files
• DirectX Shader Cache

Note: Once you’re done freeing up space on your drive, try to run the setup file again. Step 4: If freeing up space didn’t help, you can just delete the setup file and download another one from the official homepage of the program. From there download the setup file and place it in a different location. After that, run the setup file once again. Step 5: Make sure that you have downloaded the correct setup file according to your operating system, i.e. x64 or x86. Step 6: Restart your computer once more and make sure that you sign in as administrator. After that, right-click on the setup file and click “Run as administrator”. If it still didn’t help, you might want to take ownership of the folder where you saved the setup file. How? Follow the steps below but before you do that, you have to create a System Restore Point first, once that’s done, proceed.

• First, locate the concerned folder and right-click on it then select Properties.
• Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
• After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
• Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
• Now edit the permission to Full Control for “Everyone”.
• Click OK to save the changes made and then exit.

There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:

• Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
• 0x80041010 WBEM_E_INVALID_CLASS
• When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
• Trying to use wbemtest , and it hangs
• Schemas/Objects missing
• Strange connection/operation errors (0x8007054e)

To verify if there is corruption, you can try running the following command in an elevated Command Prompt:

winmgmt /verifyrepository

 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

• Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
• After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository

The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.

• Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository

This command will perform a consistency check on the WMI repository.

• If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository

This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:

• AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
• AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs

Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:

• First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
• If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
• Next, type and enter this command: Winmgmt /resetrepository
• After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
  • net stop winmgmt /y
  • Winmgmt /resetrepository

This should fix the problem.

If you encounter the MUP_FILE_SYSTEM Blue Screen error with a value of 0c00000103, then it indicates that the multiple UNC provider or MUP has got an invalid of unexpected data. This can lead to the fact that the MUP cannot channel a remote file system request to a network redirector, the UNC, or Universal Naming Convention provider. There are several ways you can fix the MUP_FILE_SYSTEM Blue Screen Error on your Windows 10 computer, you can try to check the hardware of your computer physically, update or rollback some device drivers, run the Driver Verifier Manager, remove any hardware you’ve installed recently or fix issues related to IRQ. Use the given options below as reference to fix the MUP_FILE_SYSTEM Blue Screen Error.

Option 1 – Try to physically check the hardware

The first thing you can do is to check the physical status of the hardware in your computer. You can clean the dust off the hardware components like the Network Card of the computer. You might want to use a small blower or you could also use a soft cloth and run the components gently. Make sure that you don’t damage any parts with moisture or cause harm to any circuits while you carry out this task.

Option 2 – Try to rollback, update several device drivers

You can try to roll back, update or disable certain device drivers on your computer to resolve the MUP_FILE_SYSTEM Blue Screen error.

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the device drivers related to the Network Card, Chipset, Disk Drive, and the Graphics Drivers and any other driver related to MUP.sys and SwapBuffers.sys system files
• After that, right-click on each entry of the device drivers and select the “Update Device” option from the menu.
• Now follow the next on-screen instructions that appear and then restart your computer.
• After restarting your computer, check if the Stop error is now fixed.

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 MUP_FILE_SYSTEM 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 – Try to disconnect or disable newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the MUP_FILE_SYSTEM Blue Screen error.

Option 5 – Try fixing IRQ-related issues

The Stop error might have something to do with an issue related to IRQ. You can verify it by switching your PCI Cards around. Aside from that, you can also check if the IRQ2 is assigned to a COM Port that is unavailable at that time.

Option 6 – 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 MUP_FILE_SYSTEM. It can be found in 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.

Option 7 – Perform a System Restore

Performing System Restore might help you in fixing the Blue Screen 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.

As of the time of writing this article you no longer need or are required to have a password if you plan to log in to your Microsoft account. Microsoft explored various options for account security and came to the conclusion that passwords are obsolete. Microsoft is letting you access your account through the Microsoft Authenticator app, Windows Hello, a security key, SMS verification, or email verification code. All of these methods are way better in terms of security than passwords.

How to turn these features on?

To get rid of your Microsoft password, the process is simple. You simply need to go to your Microsoft account, click “advanced security options,” then “enable passwordless accounts” under the Additional security section.

Each time we turn ON our computer or wake it from hibernation we are greeted with a Windows login screen where we need to provide login credentials in order to get into Windows itself and start working. This method of preserving data and privacy is perfectly fine and as a matter of fact, it is recommended for mobile computers but if you have a home computer in a safe environment where no one will try to look at your data or rummage through your personal stuff then removing login screen is safe enough action and can cause you a lot piece, from time-saving to less frustration on every restart or sleep action. In previous Windows versions, it was much easier to turn off this feature but it seems Microsoft has determined that our privacy and security are important and somewhat removed the ability to turn OFF the lock screen. In this guide, we will show you how you can still remove the lock screen and automatically log in with your account like in the good old days. The first thing you need to do is to press ⊞ WINDOWS + R  to bring up the Run dialog In the dialog, type in netplwiz and press ENTER. You will find yourself in the User Accounts window, inside deselect Users must enter a user name and password to use this computer. Press OK Sign in the window will pop up where you will have to type in your password and confirm it in order to start the feature. After typing in your password and confirming it, press OK. That's it, next time you wake your computer from hibernation or turn it ON, you will automatically be greeted with a desktop instead of a Windows login screen.

The GeForce Experience on graphics card manufactured by NVIDIA is an advantage for users who loves gaming as it makes enhances users’ gaming experience. However, there are times when it may also encounter some problems. One of the problems users may encounter is the error code 0x0001. This kind of error occurs when users open the NVIDIA GeForce Experience utility. Here’s the full content of the error message:

“Something went wrong, try rebooting your PC and then launch GeForce Experience, ERROR CODE: 0x0001.”

Errors like this one diminish the overall experience of users due to the fact that when this error occurs, the NVIDIA GeForce experience wouldn’t even start which renders its features useless. There are several potential fixes you can check out to resolve this error but before you check them out, you can try to restart your computer first and then open the NVIDIA GeForce Experience once again, if you still encounter the error, then you need to check the NVIDIA Display Driver Services or update your NVIDIA display drivers or switch to the BETA release. You could also try to install and reinstall the NVIDIA display drivers or perform System Restore and see if it helps. For detailed instructions, follow the given options below.

Option 1 – Try to check the NVIDIA Display driver services

• Tap the Win + R keys to open Run and then type “services.msc” in the field and hit Enter to open the Services Manager.
• From there, look for the following NVIDIA services and make sure that their Startup types are as follows:
  • NVIDIA Display Container LS – Automatic
  • NVIDIA NetworkService Container – Manual
  • NVIDIA LocalSystem Container – Automatic
  • NVIDIA LocalSystem Container – Automatic
  • NVIDIA GeForce Experience Service – Automatic (Delayed Start)
  • NVIDIA Geforce Experience Backend Service – Automatic (Delayed Start)
  • NVIDIA Telemetry Container service – Automatic
• Next, double click on each one of the services and go to Properties. Here, check if the service is running. If it’s not, just click on the Start button. On the other hand, if they’re already running, just click on Stop and then click on Start again.

Option 2 – Try to update the NVIDIA Display drivers

You can also try updating the NVIDIA display drivers as it might help in fixing the error. To update them, follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next type in “dxdiag” in the field and click OK or hit Enter to open the DirectX Diagnostic Tool.
• From there, you can see what type of NVIDIA graphics card that your system is on.
• Take note of your graphics card information and then look for the best drivers for your operating system. Once you’ve downloaded and installed the file, restart your PC.

Note: If you want to try out the beta release of the NVIDIA display drivers, click on this link. Beware though that the beta software is unstable and buggy and may cause some different bugs.

Option 3 – Try to roll back the driver to the previous version

If updating the NVIDIA display drivers didn’t work for you, then it’s time to roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh.

• Tap the Win + R keys to launch the Run window and then type in the “msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the NVIDIA Drivers and expand it.
• Next, select the driver entries that are labeled appropriately.
• Then select each one of them and double click to open a new mini window.
• After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of the NVIDIA Drivers.
• Now restart your computer to successfully apply the changes made.

Option 4 – Try to run System Restore

You could also run System Restore as it might help fix the error code 0x0001 in NVIDIA GeForce Experience.

• 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 then check if the error code 0x0001 in GeForce Experience is now fixed.

Option 5 – Do a clean install on the NVIDIA driver

• Before you do a clean install on the NVIDIA driver, you have to download the latest version of the Display Driver first.
• Boot your Windows 10 PC into Safe Mode.
• After that, double click on the executable file of the Display Driver Uninstaller to run and install it.
• After the installation, open the program. Once you do, you should see the following window on your screen:
• In the program window, click on the “Clean and restart” button.
• After your PC has rebooted, download the NVIDIA drivers.
• Then select your Product Type, Product Series, Product, Operating System, and Language appropriate for your hardware specifications as well as personal requirements.
• Next, click on Search to display the latest available driver as per the information you entered.
• And click on Agree and Download to start downloading the latest driver executable file.
• Run the executable file after you finished downloading the latest driver executable file and then select Custom and click on Next.
• Afterward, select “Clean Install” and proceed. Doing so would install the latest driver on your PC.
• Restart your PC and check if the error’s now fixed. If not, you can try installing an older version of the driver instead.

Error Code 0x80131700 - What is it?

0x80131700 is a Windows 7 error that occurs when there is a problem with the Troubleshooting Wizard. The wizard fails to function and with an error message displaying the following message on the computer screen:

‘An unexpected error has occurred’- The troubleshooting wizard can’t continue

Error code: 0x80131700'

Windows 7 features Troubleshooting Wizard, an automated tool that helps users resolve several PC-related problems such as accessing shared files or internet connectivity to name a few.

Error Causes

The error code 0x80131700 largely occurs because of two reasons:

• The .NET framework is not properly installed on your system
• Mis-configured System Files and Registry Issues

Further Information and Manual Repair

0x80131700 Windows error is rated easy to fix error code. Thus, repairing this error code is not difficult. It is so easy to fix that you don’t need any technical expertise or professional help for that matter. To begin with, there are 2 methods to resolve the 0x80131700 error code. Let’s take a look at the solutions:

Cause: The .NET framework not properly installed on your system

Solution: If the underlying cause for the error code 0x80131700 is the improper installation of .NET framework on your PC, then the best and easy way to resolve this error is to reinstall it. By default, the built-in version of the .NET framework in Windows is 3.5.1 to reinstall this again on your system follow the steps given below:

1. Go to the Start menu and type: features in the search box
2. Now Choose the option ‘Turn Windows Features on or off’ and then press Enter
3. After this, look for Microsoft .NET framework 3.5.1 and uncheck the box
4. Once you uncheck it, restart your computer
5. Repeat the step 1 and 2
6. Now check the box before .NET framework 3.5.1
7. Restart your system
8. Now try using the Troubleshooting Wizard.

Cause: Mis-configured System Files and Registry Issues

Solution: If the error code 0x80131700 triggered due to misconfigured files and registry issues, then the easiest way to fix this error on your system is to download Restoro

Windows comes with a built-in backup solution. However, if it failed because of an internal error, you will encounter an error message saying, “The backup application could not start due to an internal error, Server execution failed (0x80080005)”. When you get this kind of error, it means that it did not start and the process failed with a Server execution error. If you got this kind of error worries not for this post will guide you in fixing the problem in your Windows 10 computer. The Windows Backup service is an excellent feature in Windows that only works on the NTFS file system and if you want to use this make sure that you have formatted your files system to NTFS. It is performed by the Volume Shadow Copy, all you have to do is right-click on any folder and if you see the “Previous versions” option, this means that a backup process runs from time to time and can bring back old files when needed. To resolve the “The backup application could not start due to an internal error”, here are two suggestions you can check out.

Option 1 – Check if the Volume Shadow Copy service is running and restart it

The first thing you need to do is check if the Volume Shadow Copy service. To do that, refer to the following steps:

• Click on Start and type “cmd” and right-click on Command Prompt from the search results.
• Then select the “Run as administrator” option to open Command Prompt with admin privileges.
• After that, type “net stop sdrsvc” and hit Enter to execute the command in stopping the Volume Shadow Copy service.
• Next, type the “net start sdrsvc” command and hit Enter to start the service again.

Note: You can also restart the service using the Windows Services Manager.

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
• From there, look for the Volume Shadow Service (sdrsv) from the list of services. Its Startup type should be set to Manual by default.
• Restart the service and if you don’t encounter any error while you turn it on, re-run the backup service and see if the backup process runs successfully.

Option 2 – Try to run the Volume Shadow Copy Service in a Clean Boot State

If the first option didn’t work and the service still keeps on failing even though the service is running, you can try putting your computer in a Clean Boot State and then try to run Windows Backup again.

• 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.)
• Now try to run the Volume Shadow Copy service again and see if the process goes smoothly.

Note: You might also want to delete all the files in the backup solution if you want to start fresh with the backup solution. Just go to C:/System/Volume/Information/Windows Backup and take ownership of the folder. After that, make sure to stop the Volume Shadow Copy service and then delete all the files inside it.

So far I believe each person on this planet has at least heard of Marvel superhero movies, perhaps even watched a few of them, and no wonder. Movies are spawning now over 20 titles and they are not really released as events described in them. Throw into mix TV series and you can get confused pretty fast. Now it was officially stated that all TV series that were released before Wanda vision is no canon in Marvel cinematic universe which simplify thing a little but there are still series that are.

So without further blabbering around here is a list of Marvels films and TV series in chronological order:

• Captain America: The First Avenger
• Captain Marvel
• Iron Man
• Iron Man 2
• The Incredible Hulk
• Thor
• The Avengers
• Iron Man 3
• Thor: The Dark World
• Captain America: The Winter Soldier
• Guardians of the Galaxy
• Guardians of the Galaxy Vol. 2
• Avengers: Age of Ultron
• Ant-Man
• Captain America: Civil War
• Spider-Man: Homecoming
• Doctor Strange
• Black Panther
• Thor: Ragnarok
• Ant-Man and The Wasp
• Black Widow
• Avengers: Infinity War
• Avengers: Endgame
• WandaVision
• The Falcon and The Winter Soldier
• Spiderman: Far From Home
• Loki

And there you go, if you have someone who has not yet seen movies or you would like to view that as the story is revealed and not by the date they were released now you can easily with this list.