-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/PF gives "Invalid parameter" error #21
Comments
That's correct because the order of the arguments and options is mandatory. Run the tool with
|
Sorry! I missed your reply before I edited my original post. I figured out I had the argument in the wrong place, and then ran into a new issue as above. But as for the order of arguments point, I get no error message with pubst /P so maybe an update to recognize that also as an out-of-order parameter? |
The command Regarding the second issue Can you remove the entry with the command |
Results (non-elevated or elevated, same):
But regardless, the 'K drive' is working and giving me no trouble—I don't seem to need whatever /PF offers. |
I need to understand or become closer in understanding what's wrong in your situation. Would you be perform the following steps:
Share results here. |
Sorry for not replying earlier. Still pretty busy so can't promise prompt feedback but here you go— Results (tempfile listing -- note that there is no entry for K )
|
@JoanEliot, I guess, the user you work with doesn't have writing permissions in the particular subkey. Let's try one more attempt.
Capture the results of all commands you execute in this attempt and share. |
Originally I thought there was a problem with /PF because I got an error when using the parameter in the wrong place.
This is incorrect:
psubst /PF K: C:\z\K
(but
psubst /P K: C:\z\K
did not throw an error)Now I have an error when using /PF in the right place:
C:\util>psubst K: C:\z\K /PF
psubst: Unable to add persistently SUBSTed drive
However, pubst /P reports the drive as present, despite the error. Does that mean I have a SUBSTed drive with the features of a /P persistence, but not those expected with /PF?
The text was updated successfully, but these errors were encountered: