Can’t print a file, it opens Save as option

Recently, a number of Windows 10 users getting an error on their computers that state, “Windows can’t find one of the files in this theme”. According to the affected users, this error occurs at random times even when they didn’t make any changes to their computer’s theme prior to getting the error. If you are one of these users, read on as this post will help you resolve this problem. If you click on the Yes button of the dialog box where the error is displayed, it won’t fix the problem as you will still get the same error from time to time. This kind of error could be caused by the executable file named “SettingSyncHost.exe”. It is possible that this executable file is unable to sync your theme all over your computer. On the other hand, it could also be due to some problems with the active theme. To resolve this issue, you can try to change the active theme, or disable the custom screensaver or disable theme syncing on your computer, as well as run a System File Checker or run the DISM tool. For more instructions, follow the options given below.

Option 1 – Try to change the active theme

The first thing you can do to fix the error is to change the active theme of your computer since the SettingSyncHost.exe file might not be able to properly sync the theme on the computer.

• Go to Settings and click on Personalization.
• Next, click on Themes and scroll down to apply a theme, and change the theme of the operating system.
• After that, tap the Win + R keys to open the Run dialog box and type “%windir%ResourcesThemes” in the field, and then tap Enter to open the folder where the theme files are located.
• Once you’re done, right-click and select delete for the active theme to remove the theme and its resources. This should fix the root cause of the problem. If not you can try to create a new Windows 10 theme and save it.

Option 2 – Try to disable the custom screensaver

The custom screensaver is a part of the mechanism of the lock screen. Although they were needed in the earlier Windows versions to prevent the discoloration of CRT monitor screens, they are no longer needed in the current version of Windows. Thus, you can try to disable it as it could be the one that’s causing the problem.

• Click on the Start button and go to Settings > Personalization > Lock screen.
• Here, scroll down and click on the Screen Saver settings.
• After that, select the “Screen saver to (None)” option from the drop-down menu. This will disable the custom screensaver.

Option 3 – Try to disable theme syncing on your computer

You could also try to disable the theme sync feature to fix the problem. This has worked out for some users. To do so, follow these steps:

• Click on the Start button and go to Settings > Account > Sync your settings.
• From there, toggle off Themes in the individual sync settings column. This will disable the Theme syncing.
• Restart your computer and see if the problem is now fixed.

Option 4 – Run the DISM tool

The next thing you can do is run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like the “Windows can’t find one of the files in this theme” error. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the problem is now fixed.

Option 5 – Run the System File Checker

System File Checker or 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 to good system files that might be the cause why you’re getting the “Windows can’t find one of the files in this theme” error. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• 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 and see if the problem is fixed or not.

System restore is usually the go-to tool when something goes bad in Windows, we fire it up and roll back Windows in the state when everything was working fine. But what if Windows does not want to boot? Can we use system restore in that case? The answer to that question would be yes, yes we can.

1. Boot interrupt Windows 10 by starting your PC and as soon as you see the Windows logo; press and hold the power button to force a shutdown.
2. Repeat this 2-4 times and Windows will open up the Advanced Startup Options menu for you.
3. At the Advanced Startup Options screen, select Advanced Options.
4. Select Troubleshoot.
5. Under the Advanced options screen, select System Restore.

or if you prefer, use Windows USB installation.

1. Boot the faulty PC using the Windows 10 installation media.
2. The Windows Setup dialog box will appear.
3. Set the Time and currency format, Keyboard or input method, and the language to install.
4. Click Next.
5. Click on Repair your computer from the lower-left corner.
6. From the Choose an option screen, click on Troubleshoot.
7. Click Advanced Options in the Troubleshoot screen.
8. In the Advanced Options screen, click System Restore.
9. Windows will take some time to prepare System Restore. It may even restart your computer or device.
10. When System Restore is ready, you will be prompted to choose a user account to continue.
11. Select an account that is set as administrator on your Windows 10 computer or device.
12. At the next screen, change the keyboard layout if you want and then input the password for that account.
13. Click the Continue button.

Recently, several users reported an issue on their Windows 10 computers where the taskbar is not visible when they tried to connect to a computer via Remote Desktop Protocol or RDP. The Remote Desktop Connection feature uses the RDP which allows users to access a computer remotely. This is actually different from the taskbar being hidden automatically until the pointer hovers on it since, in this scenario, the taskbar is completely not accessible which makes using the remote computer entirely difficult, if not impossible. There are several suggestions you can check out to resolve this problem, you can try to restart the process of Windows Explorer via Task Manager or you could clear the cache for multiple processes. You could also try to reinstall the Shell Experience components or show the local taskbar in the Remote desktop. Moreover, you could also try to update, uninstall or roll back the display driver/graphics card driver. For more details, refer to each one of the options given below.

Option 1 – Try to restart the Windows Explorer process

The first option you have to try to fix the problem with the taskbar is to simply restart the Windows Explorer process in the Task Manager.

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and find the process of Windows Explorer.
• Once you find it, right-click on it and select Restart to restart its process.
• After that, restart your computer and see if you can now see the Taskbar.

Option 2 – Try clearing the cache of multiple processes

The next thing you can do to resolve the problem is to clear the cache of many processes in your computer. To do so, follow these steps:

• Open the Notepad app and paste the following content in the text area:

@echo off taskkill /f /im explorer.exe taskkill /f /im shellexperiencehost.exe timeout /t 3 /NOBREAK > nul del %localappdata%PackagesMicrosoft.Windows.ShellExperienceHost_cw5n1h2txyewyTempState* /q timeout /t 2 /NOBREAK > nul start explorer @echo on

• After that, tap the Ctrl + S keys to save the changes you’ve made in Notepad and select the “All files” as its file type, and then name it “CacheClearTWC.bat”.
• Next, go to the location where you saved the file using File Explorer and then run it. This will run a couple of batch scripts which will clear the cache of multiple processes in the system.
• Tap the Win + X keys and select the “Windows PowerShell (Admin)” option to open PowerShell as admin.
• Next, execute this command in the command line: Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “appxmetadataappxbundlemanifest.xml”)}
• After the command has been executed, this will reinstall the Shell Experience components and should fix the problem with the taskbar.

Option 4 – Update, uninstall or rollback the Graphics card drivers

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in 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 Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

One of the most common and bothersome issues with a printer is when it refuses to get configured or set up on your computer. Thus when your printer has some configuration issues, you will most likely encounter the error 0x00000709. This occurs if there is already a default printer set and configured or Windows does not want to configure the new printer at all. The operation could not be completed (error 0x00000709), Double check the printer name and make sure that the printer is connected to the network. Today, we will try two fixes that may help you get rid of this error.

Option 1 – Run the Printer Troubleshooter

One of the first basic troubleshooting you can perform to resolve the printer issue is running the Printer Troubleshooter. This built-in troubleshooter can detect and automatically fix the problem for you. To use it, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• Next, type “exe /id PrinterDiagnostic” in the field and click OK or hit Enter to open the Printer Troubleshooter.
• Then click the Next button and follow the next on-screen instructions to fix the issue with the printer.

Option 2 – Try to use some Registry tweaks to add the Printer

You might want to use some tweaks to add the Printer but before you proceed, make sure to create a System Restore Point so that if anything goes out of hand, you can always undo the changes you’ve made.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “Regedit” in the field and hit Enter to open the Registry Editor.
• When a UAC or User Account Control prompt appears, click Yes.
• Once you’ve opened the Registry Editor, go to the following key location:

HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionWindows

• From there, double click on the file named “Device on the right side pane under the Windows folder.
• Now add the name of your printer in the Value Data field as you can see below and then click the OK button.

Note: As you can see on the image above, you must not change the “.winspool.Ne02:” part and only the first one which is the name of your printer.

• After that, you will get a message that says, “Cannot edit Device: Error writing the value’s new contents, simply click on OK again. You have to take note of the existing permissions before you proceed to the next step. Once you’ve added the Printer, make sure to reverse the changes you’ve made to the Permissions.
• Now right click on the Windows folder located on the left pane and click on Permission.
• Select Restricted under the Group or user names section.
• Then check the checkboxes for “Full Control”, “Read” and “Special Permissions” under the Permissions for RESTRICTED section.
• After that click the Apply button and then OK to save the changes made.
• Next, right-click on the file named “UserSelectdDefault” and select Rename to rename it to your printer’s name.
• Now restart your computer to successfully apply the changes made.
• After the printer is added, don’t forget to reverse the Permission changes you’ve made early on.

Option 3 – Try updating the Printer drivers

You might also want to try updating your printer drivers. All you have to do is locate the USB Composite Device. For complete details, follow the steps below.

• 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 USB Composite Device option and right-click on it, and select the Update Driver from the options.
• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: You also have the option to download the latest version of your Printer from the manufacturer’s website.

What is Error Code 1309?

Error code 1309 is an error code that occurs when installing either Microsoft Office 2003 or Microsoft Office Project 2003. This error code may hamper your ability to run and use applications associated with Microsoft Office. To ensure installation is successful, it is first advisable to fix this error code. Error 1309 is displayed in any one of the two formats illustrated below. When installing Microsoft Office Project 2003, the error message may pop up as:

Error 1309. Error reading from file:    pathfilename.cab. Verify that the file exists and that you can access it.

When installing Microsoft Office 2003, the error message may appear in the following format: Fatal Error During Installation

Solution

Error Causes

Error code 1309 message may appear during Microsoft Office installation due to several reasons. These include:

• Problems in the Oclncore.opc file. Project 2003 uses this version of the file for program installation.
• Lack of adequate use permission
• The requested file was not found
• Setup registry entries are modified in an unacceptable manner

To avoid inconvenience and access Microsoft Office 2003 or Microsoft Office Project 2003, it is recommended to fix the error immediately.

Further Information and Manual Repair

To resolve this error you don’t need to be a technical whiz. Here are some of the best, easiest, and proven do-it-yourself methods to resolve error 1309 on your computer screen instantly.

Method 1 - Change CacheLevel Settings

If the problem is related to Oclncore.opc file then try changing CacheLevel settings. Follow these steps to work around this method.

1. First, locate the PRJPRO*.XML file in the FILESSETUP folder of the Project 2003 installation source and then open this file in the Notepad.
2. Also, make sure that you do not open the file as read-only and make sure that a checkmark is not displayed next to Word Wrap on the Format menu.
3. The next step is to search the file for the following text string: OCLNCORE.OPC_1033.
4. Now on the line where this string is located, change the CacheLevel=’1’ setting to the following CacheLevel=’3’ save the file back to the original location, and then quit Notepad.

After the changes are activated, try installing the software again on your system. If it installs successfully, then this means error 1309 is resolved. If the error still persists then try other given methods.

Method 2 - Configure security settings to get full permission

When the cause of error 1309 on your PC is related to lack of adequate permission issues, then configure security settings to resolve. To do this, simply locate the folder on your installation drive. Then right-click the folder and click Properties. On the Security tab, click edit and now make sure your user name is added to the list. Grant required security permissions and then click OK to save changes. After this, try installing Microsoft Office 2003 again on your system.

Method 3 - Copy the requested file from another source

If the error 1309 pops up because the requested file was not found, then try this method. Simply copy the file specified in the error to the destination directory. For example, if the error shows data1.cab was not found, then copy this file from another source and paste it into the directory specified in the error description.

Method 4- Remove bad registry entries

Bad registry entries are responsible for registry setup modification. If this is the reason for error code 1309, then download Restoro. This is a user-friendly PC Repair Tool embedded with a powerful registry cleaner. It scans and removes all bad and invalid entries accumulated in the registry. It cleans and repairs the registry resuming it back to its normal function. Click here to download Restoro and repair error 1309 today.

Runtime Error 429 - What is it?

Error 429 is a type of runtime error. It sometimes occurs when you use the new operator or the CreateObject function in Microsoft Visual Basics to create an instance of a Microsoft Office application. The error code is displayed on your computer screen in the following format:

Runtime Error ‘429’: Active X component Can’t Create Object

Solution

Error Causes

The runtime error code 429 is triggered for several reasons. These include:

• Mistake in the application
• Incorrect system configuration
• Missing ActiveX components in the application
• Damaged Active X and class application components
• DLL required by the application is damaged
• Active X object was not registered properly
• Corrupted applications
• Corrupted Windows registry
• Class ID issues

The runtime error code 429 not only causes you inconvenience as it hampers your ability to access programs but delays in repairing this error code can lead to serious PC damages such as system freezes, crashes, and failures.

Further Information and Manual Repair

To resolve the runtime error 429 on your PC, try the following recommended solutions:

1. Re-register the Application Causing the Error

Identify the Office application causing the error and re-register it. For instance, if Office Excel is the prime cause of the error message pop up, simply re-register it. Click on the start menu and then run. Then type this in “: C:/Program Files/Microsoft Office/Office/Excel.exe /regserver” and press OK. This will hopefully resolve the issue.

2. Go to The Microsoft Windows Script Update Page and Download Microsoft Updated Installation File

This will also assist you in repairing runtime error 429. Simply follow the installation wizard and update your MS Office Applications. The corrupted files and missing components in them would be easily corrected by the update file. However, if this doesn’t work, then this means that the cause is more crucial than you think. It is either related to damaged Active X objects or a corrupted Windows registry.

3. Repair the Active X objects and the Registry

To repair both the registry and the Active X objects in one go, it is advisable to download Restoro. This is an advanced, next-generation, highly and multi-functional PC repair tool. It is deployed with powerful and numerous utilities like a registry cleaner, Active X and class scanner, privacy error detector, and system stability module. The registry cleaner embedded in this repair tool enables you to wipe out obsolete, unnecessary, malicious, and invalid files and registry entries saved in the registry. It frees up your disk space, repairs damaged DLL files and the registry thus resolving the runtime error 429 on your system. The Active X object and Class feature identifies and scans Active X issues on your PC and resolves them right away. Besides this, with this error tool, you can also scan for viruses and also improve your PC performance.

Why Total System Care?

Total System Care is a one-stop solution to resolve all kinds of PC-related issues including the runtime error 429. To run it on your system, you don’t have to be a computer programmer. It is very easy to operate. It has easy navigation and a user-friendly interface. There is nothing complex about it. It is safe and efficient. It resolves all PC issues in a few seconds. You can run it in the background while performing other tasks on your system. Furthermore, it is compatible with all Windows versions. Click here to download Total System Care and resolve the Runtime Error 429 on your system today.

There are a lot of online services and a lot of ways to get your public IP address. One of them being typing whats my IP in Google search and you will get immediate results. But there is a way to get the same information inside Windows 10 which could be very useful if for any reason you can not connect to mentioned services. By checking public IP directly inside your windows you can make sure that the issue for not being able to open some websites is not due to your public IP. In order to use this Windows feature, we will be checking our public IP using Windows PowerShell. To open Power Shell in Windows first press ⊞ WINDOWS + R to open the run dialog Inside run dialog type Powershell and press ENTER In the Powershell type in the following command and press ENTER

(Invoke-WebRequest -uri "http://ifconfig.me/ip").Content

When the command finishes you will see what is your public IP address, if you wish to know more about your connection type in and press ENTER:

Invoke-RestMethod -Uri ('https://ipinfo.io/')

This command will provide you with further information like city, region, country, and others.

Windows PowerShell is a powerful tool inside the Windows environment often overlooked by typical users which is a great mistake since it can offer a large array of functionality and usability and if used well can offer a unique working experience. Today we will be using PowerShell to turn the WEB camera off so it can not be accessed, completely disabling it for use. You might want to do this for security reasons or just want to learn few new things. Whatever your reason might be, I am welcoming you to this tutorial and please do keep reading.

Finding device ID

In order to disable the WEB camera first thing we need to do is to find a matching device ID. We will find this value inside the device manager, so press ⊞ WINDOWS + X to open the secret menu. In the menu choose device manager and click on it. When the device manager opens, expand the Imaging devices or Cameras section. Right-click Integrated Camera or the primary webcam, and click Properties. Go to the Details tab. Under the Property section, click to select Matching device ID from the drop-down. Right-click the value and select Copy The next step is to download and install Windows Driver Kit (WDK)

PowerShell script

Create and run a PowerShell script with the following parameters/values to disable the camera. Substitute the <FOLDER> placeholder with the actual name of the folder where your copy of Devcon is residing

$id = (Get-CimInstance Win32_PnPEntity |

where caption -match '<PRIMARY CAMERA>').pnpDeviceID

$ppid = "{0}{1}" -f '@',$id

Set-Location c:\<FOLDER>

Devcon status $ppid

Devcon disable $ppid

Devcon status $ppid

To enable the camera device, run the command below in PowerShell:

devcon enable $ppid

Things have stirred lately with Chinas ban on crypto mining and many used GPUs will flow the market probably. But should you buy a used GPU? Short answer: NO, long answer: keep on reading to find out why.

GPU shortage and its cause

As you all know by now, we live sadly in a world struck by a global Pandemic. Due to this awful disease and measures taken against it, many people are either working from home or are at home making the manufacturing of new chips problematic while demand on the market has raised. Throw into that mix crypto mining which has raised in popularity and you have, well today's market where we have GPU shortage. Now with the latest news that China has banned the mining of cryptocurrency, there is to be expected that at some point in time mining cards used there will fit the market in the whole world. Sadly even with a large quantity of GPUs that will become available, the overall price of cards will not be much lowered I am afraid since demand is still very high and many people would not want to purchase used mining cards and neither should you.

Be prepared for the worst scenario

Although this sounds very pessimistic and in most cases, it will not turn out to be true, you should always prepare yourself mentally that you might be in that lower percentage that will end up with a really bad GPU. What has come up to be absolutely true when considering GPU that were mining is that if anything at all can be done to GPU in order to increase performance, it has been done. Miners want to optimize and almost every GPU if could be overclocked, it was overclocked. Extensive mining also means that thermal paste has been dried and it is pretty useless at this point and there is a very high chance that fans and heat sinks will need much cleaning or even replacement raising the price of the card itself for mentioned paste, fans, and heat sinks. There's no way to tell what the previous owner might have done with a graphics card when you're shopping online, so our advice is to assume the worst. Don't trust the seller to give truthful information. Any listing that says it was "never used for mining" at this point is probably a lie.

Age of the GPU matters

Date when GPU itself has manufactured really matters. Newer cards even if used extensively have been used for a much shorter period of time and are not so damaged were ones produced a few years ago have seen a lot of action. Let’s say that you get RTX 3060, In the worst-case scenario it has been mining since late February of 2021 and basically, it is still under warranty so it should behave OK and put some good work in gaming even in that state. On another hand, if we take for example GTX 1080Ti which is 4 years old GPU things start to change drastically. 4 years GPU could be worn out even if it was used just for extensive gaming sessions let alone for mining.

No return policy and seller rating

Most of the time you will run into a product that cannot be returned or no refunds policy. This should bring a red flag right away and deter you from purchase. Sellers with the highest ratings are more trustworthy since many of them will not want to destroy their reputation but these will probably not even have these kinds of merchandise in their store. Buying with a poor rating seller and no return policy on a product is just asking for trouble. And although some stores do have arbitration and will stand on the customer side there is no guarantee for that and it will take too much time to process.

If you really must buy a second-hand GPU

Of course in these troubled times sometimes due to malfunction or any other reason, there would not be another choice than to buy a second-hand GPU. In this case, if there is no other option consider sellers with many positive ratings. If you can buy locally that would even be better or the best-case scenario would be if you could visually see and inspect GPU itself in order to see in what state it is. Look for warranty stickers to see if they are thorn and the card has been tampered with. Also take a good look at screws, if they have scratches card has been opened, probably to replace fan or heating sinks which means that it has worked a lot.

Conclusion

It is very difficult to give the best possible advice on this situation since of GPU shortage, but I would much prefer a new GPU with lower performance than a hi-performance one which was mining.

When performing a Windows Backup to the NAS device (backup to a network share) that is running Samba, fails with an error message The backup failed, The version does not support this version of the file format (0xC03A0005). The problem occurs because of a conflict with the VHD file that is created by Windows Backup and is mounted during the process. There are three types of VHD files:

1. Fixed,
2. Expandable
3. Differencing

If the VHD file is a sparse file that is not supported by the native VHD driver, the mounting will fail, and you will get this error. An example VHD file is one that keeps expanding depending on the backup size. The problem occurs only in the case of  File Level backup (file/folders in a volume) but not on the block level backup as the vhd file is never mounted. However, in the case of File Level Backup, the vhd is mounted, created by Windows Backup, which does not support the mounting of sparse files.

The solution is to use Strict Allocate: option in the smb.conf file

Login to SMB using SSH. Open the configuration file using the VI editor located at /etc/samba/smb.conf. If the option is not there, you can manually add strict allocate = yes which will make sure there are no sparse file that is created.