Finding files via File Explorer can be a really slow and tedious process and if you are searching often it can accumulate a lot of time loss.
I am a person which often has assets for projects in several different folders and altho I am trying my best to be tidy and organized sometimes I can not remember where I have placed certain assets that I need, in this case in order for me to find a required asset I usually search it via command prompt because it is lightning fast and gives results in second not minutes compared to File Explorer.
If you are in a similar position and you need fast results please read on as we dive deeper into the command prompt and its usage.
To quickly open the command prompt press ⊞ WINDOWS + X to bring Windows secret menu and choose the command prompt, you can also choose the admin version but for sake of this specific task, there is no difference.
in the command prompt you need to type the next command:
dir \search term* /s
where search term* is well, what are you searching for.
Now if you are looking for a specific file this command is straightforward, you just change search term* with file_name.extension and there you go, but know that this command can be used to be more powerful, for example, you can find all JPG files in your drive by typing dir \*.jpg /s or all files named work by typing dir \work.* /s
" * " is a so-called joker sign, it replaces several characters with any in a given string, meaning that dr*s will give you all results with the first 2 letters dr and last one s. Use this to specify better search results and you will get your files in no time.
“We couldn’t install Windows in the location you choose. Please check your media drive. Here’s more info about what happened: 0x80300002”You can encounter this kind of error if there is corruption in the partition table of the drive where the installation is in progress. In addition, corruption on the Media device could also cause this problem. So if you encounter this error when running Windows Setup, read on as this post will guide you in fixing it. There are several ways to resolve this issue. The first thing you can do is to verify the compatibility between the BIOS and the installation media. You could also try recreating all the partitions as well as recreating the bootable USB drive. For more detailed information, follow the given options below.
“This policy setting allows you to control whether a domain user can sign in using a convenience PIN. If you enable this policy setting, a domain user can set up and sign in with a convenience PIN. If you disable or don’t configure this policy setting, a domain user can’t set up and use a convenience PIN. Note: The user’s domain password will be cached in the system vault when using this feature. To configure Windows Hello for Business, use the Administrative Template policies under Windows Hello for Business.”
A runtime error is commonly an error that's created after the PC is operating software and encounters a problem of some form. For instance, a runtime error like run-time error code 7 reveals an "out of memory" dilemma.
Run-time errors are normally brought on by clashes with TSR (Terminate and Stay Resident) applications or additional operating applications, software problems, storage problems, or pc viruses.
First, enter the run-time error signal into a search engine to see what info you will get about the precise runtime issue you are receiving. Next, end - job all running applications and TSRs to make sure these aren't the origin of the issue. You can certainly do so by obtaining the job manager by striking Control Alt Delete.
In case your issue is regularly occurring with a unique program, go to that system programmer's site and obtain any upgrades and patches. If unavailable, try uninstalling the application involved and reinstalling it.
In the event the issue is occurring with the os, you may consider reinstalling it although it is a huge commitment. A much better idea would be to try a fix for both Windows XP or Windows 2,000. It is possible to fix and scan files by typing : sfc / scannow, heading to the Begin switch, Run, and then pushing enter. Make certain to put an area between sfc and the reduce.
You might have an equipment or storage dilemma if these measures have not resolved your run-time errors. If that is the situation, contact the support of the application under consideration for potential support accompanied by the pc or motherboard manufacturer.
Many run-time problems can be solved by upgrading the application that's creating the problem. This is only because the programmer's frequently releasing patches and improvements for their applications as insects are found and repaired.
Storage problems may frequently be fixed by rebooting the pc. Consider a reboot a short-term repair. Rebooting clears the memory but in case your COMPUTER does not have adequate memory for your applications you're operating, or sufficient hard-drive space you'll immediately run out of memory again. Something less than this sum may cause memory issues since the computer's swap file isn't in a position to expand in dimension as required.
To assess the quantity of free area, available My Computer and right-click on the HDD, generally the D: drive. Select Attributes in the menu and see the disc's ability. Perform the disk clean-up function by following prompts and pressing the Disk Clean-up button, if the room is reduced.
You may be getting run-time errors, in case your storage chip is really failing. Eliminating and changing the awful memory chip will solve the difficulty. If you're encountering other runtime-related errors, like an install runtime issue, try cleaning away the portions of the registry with some software solution.
/c ren %systemroot%System32Spupdsvc.exe Spupdsvc.old