To fix this issue, I attempted to change the for loop to have an additional query with two conditional &s and ||, however, this doesn't work either, because occasionally the registry key containing the string might be named HKLM\SOFTWARE\Classes\CSID\\Example, with a DWORD with the name of Name and the data value of string. Some brief reading leads me to believe that findstr can only manage so many bytes of data, and I am obviously overloading it due to the massive size of this registry hive (approx. After that, I get continues lines containing FINDSTR: Line 50300 too long, with an increasing value on the line number.
What currently happens is the script will run for about ~20 seconds with no returns in the command prompt. This works for a very specific, predetermined area of the registry - the only drawback for me is that my script needs to parse the ENTIRE SOFTWARE registry hive, which is loaded from an external drive. The code I was attempting to use is: offįor /f "delims=" %%a in ('reg query "%key%" /s^| findstr "%search%"') do reg delete "%key%" /v "%%~a" I am currently working on a batch file to delete all registry keys containing or named a specific string (yes I know the dangers of doing this), however, I'm having a few issues.
0 kommentar(er)
