Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I have tried using the "runas" command from Windows to run a program with lowered credentials than those of the currently active account (in order to "sandbox" that program to be only able to access certain directories and files).
It works fine, for the most part, but I am getting a strange error.
The command that works without any issues is:
runas /noprofile /user:<Username> <program.exe>
But when I try to remove the /noprofile and instead write runas /user:<Username> <program.exe> or alternatively runas /user:<Username> /profile <program.exe> I get an error saying (roughly translated) this:
RUNAS-ERROR: <Path-To-My-Program> cannot be executed
299: Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
I tried researching the error but the only thing I could come across was some people that encountered this error trying to work with CDs, USBs and external hard drives, and setting some registry values for those worked for them.
I did not attempt to modify the registry myself, because I am not using any of these, and thus I concluded that the error had to be something else on my end.
I am really confused as to what is causing this behaviour, and am hoping that someone who is more experienced with this can help me out :)
Thanks in advance
Best Regards
It seems that this error is commonly attributed to problems with file access. Have a look here for details on analysing the root cause of the problem.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed yesterday.
Improve this question
I have trying to learn how to do some basic networking and I have having issues using Putty. I am Connecting my server computer to the RS-232 via ethernet, and able to get the command prompt to display. However if i press enter, any characters or numbers I get nothing.
I've tried messing with the setting to see if i have something disabled. That hasnt worked for me so far, i also tried setting the speed from the default to 115200 to see if that would work either.
Am i missing a step that i need to do?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed last year.
Improve this question
How do I convert a pdf file to doc?
I tried the following:
soffice.exe --convert-to doc C:\Users\Administrator\Desktop\pdfda.pdf
When I hit enter nothing happens, I have libreoffice installed and I'm using Windows 10.
For others landing here the support advice is use soffice NOT soffice.exe since that should on Windows invoke the console command line version soffice.com
see https://ask.libreoffice.org/t/convert-docx-to-pdf-via-the-commandline-on-windows-10/64418/6
Starting from v.6.3, you should not use soffice.exe when working in terminal. You better just omit the extension (like [invoke in folder >] soffice), or explicitly use soffice.com, to use a version specifically created for console, which would output the errors, if any, to the console, instead of silently discarding any output. Also note that you should make sure that LibreOffice is not running in the background when you are launching the command line, because otherwise your command would be redirected to the existing GUI process, and you may again not see the error messages.
Alternatively, specify a separate user profile when calling command line to allow separate processes - see -env command line parameter
Full documentation is at https://documentation.libreoffice.org/en/english-documentation/
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
How can I solve it? Have no clue why that happens.
Given result
If I uncheck legacy mode the consoles stopped running: after opening the window freezes and nothing more happens (affect either PowerShell and command line):
Expected result
PowerShell and command line can be used in regular mode and are not rely to run in legacy mode.
If it runs in legacy mode but both Powershell and CMD freeze then there's probably something wrong with your windows install.
There's a variety of ways and programs you can use to try and troubleshoot (like Microsoft Sysinternals) but that's beyond the scope of what Stack Overflow is for
Here's a couple Stack Exchange sites you can ask for help troubleshooting the OS:
Super User for end user machines
Server Fault for network admins and servers
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
So that this doesn't cost you an hour of Googling around:
Problem: launching psexec (from Powershell) with
./psexec64 \targetip -s -u domain\username -p "password" c:\path\to\this\file.exe -accepteula
Result:
It seems to connect but you get All Pipe Instances Are Busy
The solution (at least in this case: The path to the executable on the target host has a typo.
Yup. No shame. We all do it. Go fix your typo and enjoy the rest of your day.
On a related note, I couldn't shake the "the handle is invalid" error from the command prompt and worked around it by going to PowerShell. Apologies for not having a good technical explanation as to why that's the case, but this has been bonus psexec material.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I know that deleting the main profile is a stupid action and it is mainly my fault. I still want to understand the consequences and issues based on my mistakes.
I did today some really silly stuff I used in my Ubuntu Terminal command sudo rm -rf taras, which deleted all the stuff that I had on my Ubuntu taras profile. I was trying to delete other account but ... forgot to modify something.
Luckily I started deploying Ubuntu 2 months ago. I am using it as a secondary OS with Windows (double booting) so none of my personal files where destroyed but my projects, savings were deleted.
Can you please explain to me what are the consequences of this? Do I need to reinstall Ubuntu again? Or I still can continue my work there? In such situations Git really helps a lot ;-)
There isn't anything fundamental in the home directory. You would still be able to boot, though possibly you would end up in a tty login prompt. Alternatively, if it boots into a login manager, logging in might produce some errors. You would still be able to login with your usual credentials.