Windows 10: Can't open any file due to "parameter is incorrect" error message

I wanted to change permissions and take ownership of my entire hard drive, for which I used a youtube video this one: https://www.youtube.com/watch?v=peS90MIUtb8&lc=UgybKwPVB4b0xnxL_l94AaABAg. During the process, for some files and folders it said access denied, or something like that. Ever since that happened, i have not been able to open any file on my laptop, as it gives me the "the parameter is incorrect" error message. I asked the creator of the video how I can solve this, they haven't replied yet. How can I solve this?

:)

 

Can't open exe files. Error message "parameter is incorrect " or " no such interface supported "

Hi

I am not able to open any exe files . I get the error message "the parameter is incorrect". When I open task manager I get the message "interface not supported ". Also no right click options work. Even widows start button doesn't works. I also see some unknowns
files on my desktop.

 

incorrect parameters

While attempting to download pictures from my Samsung phone, I received an error message that it couldn't download due to incorrect parameters. How do I fix this?

 

parameter is incorrect

On Windows 10 when I try to create a list of all files of a particular type, I get this message during the search: "The parameter is incorrect."

I have run chkdsk and sfc and find no problems. It happens more frequently when the drive being searched is an external USB drive, but also happens on the local disk. There is no explanation of *what* parameter is incorrect.

Creation of the list (a txt file) completes, with no appearance of the error messge... but I don't know if all files were found or not. Typically, this message is given when I search for a filetype of which I know there are more than 100... with the rate being
about twice per hundred files.
Example of the searches:

dir *.css /S>_allCSS.txt

dir *.html /S>_allHTML.txt
Over the weekend I tried this on 14 different systems, with different external drives. Same result. Oddly (maybe?), no such message is given when running the search on a NAS drive (tried 2 different ones), but the search takes considerably longer on the
NAS drives.

Does anybody know what causes this bizarre detail-free error message?

Any assistance greatly appreciated!