I'd like to boot VirtualBox to the external hard drive I have that runs Windows 8 To Go, as the computer running virtual box is one that I can't boot to the drive during certain hours, but I'd still like to be able to interact with the OS on that drive.
I found a guide for creating a raw VM DK disk file for my external drive, and ran the commands for it in an administrator command prompt, which was listed as a requirement in the article I was reading.
At first, I'd boot to the drive with my VirtualBox machine, and it would ask me to enter the BitLocker encryption password.
I'd enter it, and before the spinning circles of the Windows loading logo would make a complete rotation, VBox would give me an error popup saying "Error: VERR_ACCESS DENIED".
I researched the issue a bit online and found that some users had resolved this issue by turning on 'Use host I/O cache' on the VirtualBox Storage controller.
I tried this, and the machine did indeed make it farther and stopped displaying an error message, only now it stays on the windows loading screen indefinitely, or may even restart itself.
I checked the log file and am seeing several non-displayed error messages of 'VERR_ACCESS DENIED".
Running virtual box itself as an administrator has had no effect.
Has anyone else tried this successfully? Does anyone have any tips?
I'd appreciate productive suggestions instead of criticism against 'why' I'm doing something.
Thank you!
Related
I have problem printing reports to PDF through bullzip from Navision Application Server (1) if user is not in Local Admin group (2). Only under both conditions.
In Nav code I'm doing the following: init bullzip automation object (set all parameters to suppress GUI), run report to print document to virtual bullzip printer, catch output file. Thats it. Straight as a rail.
I have two environments: Windows Server 2008 and Windows 7 (different versions of Nav, but this is changing nothing). On Windows 7 it just do nothing (but works if user is admin). On server I can see error in Event Log (translated to English)
Faulting application gui.exe, version 9.8.0.1599, time stamp 0x517126dc, faulting module USER32.dll, version 6.0.6002.18541, time stamp 0x4ec3e39f, exception code 0xc0000142, fault offset 0x0006f52f, the process ID 0x3bc, application start time 0x01ce562238369fa9.
Gui.exe is a part of bullzip.
If I run the same code from Nav Classic Client, or from the same NAS launched in command line, or under local administrator account, or if i put the NAS user in local admin group - it works just fine.
To solve this problem i need to find out one of two and how to fix it:
What is the difference between local admin and regular user that could cause application to crash in non-interactive mode (service) under regular user account.
What is the difference in running NAS as service and as command line that could cause application to crash when run as service.
What I've tried so far: extend non-interactive desktop heap, give user all local privileges that admin have in gpedit. Not works. Don't know direction for further digging.
Any alternative free pdf printers advices are welcome.
This question is still actual. Though I've managed to setup PDF printing with PDFCreator. The tough part was to let several different NAS to print simultaneously. And now the setup have a bottleneck - PDFCreator's printing queue. With bullzip automations it could be avoided.
We've had some cases where third party DLL's have crashed within NAV due to permission restrictions.
The only effective way we could narrow down the files that it was trying to access was through using Process Monitor to try narrow down what was causing permission issues.
We found a folder within System32 to do with the System's Network Profile that some DLLs use. On that note, NAS's and such should be run under a domain account.
I think re-installing the application will do that,
Just make sure you are uninstalling each bullzip and ghost script,
Now Ghost script is tricky thing, if you are installing 32 bit over 64 then you are having problem,
refer this download link download appropriate version, install it,
and then install bullzip, after downloading new version from here
this will do..
then also if any problem(if you are using application for automation, you require new com object..) refer Forum, that explains most of application interface problems..
where you need to use public class PdfSettings with namespace bioPdf.
I hope this will help ..
I have a Windows 7 Ent - 64bit system.
I am stuck in a loop, where the login screen is presented, i enter my network credentials, the welcome spinner is shown, the screen flickers like when resized, then the system goes to logging off screen and then finally goes back to the control alt delete screen.
I cannot get out of that loop for the life of me.
I contacted corp support, he came over and logged in using his login (admin level) and was able to get a desktop up.
The support people are not allowed to access the registry to correct or even look at my users settings, and my user IS NOT AN ADMIN on this machine.
Question is - is there a way to blow away my profile on this machine, or reset my registry branch to that of a new user or something???
i have bitlocker enabled on the drive - so using the emergency boot disks are almost rendered useless...
im stuck, and i dont know where to look....
any ideas would be wonderful
thanks
the admin level user logged in, and turned his back for a moment, and i was able to go in and reset the autologon registry entry...
rebooted,and all is well.
Disconnect Your USB Devices
If you like using all sorts of USB devices such as the mouse, keyboard, speakers, Bluetooth speakers, USB dongles, USB Wi-Fi adapters etc. However, these connected devices might cause the Windows 7 stuck on the welcome screen for a long time issue. Therefore, a common solution to the problem is to disconnect all externally connected devices from your PC.
Disconnect from the Internet
Sometimes Windows 10 gets stuck on the login screen because it's trying to connect to your wireless connection. If your Windows gets stuck on the welcome screen, you should make sure that you are not connected to the internet before proceeding to log in.
Run system checks
In some case, corrupt system files on your computer will cause this problem – stuck on welcome screen Windows 10/8/7. Therefore, to fix the Windows 10 freezes on startup problem, you can use CHKDSK to run some checks on your computer to see if it is the corrupted files that cause your startup problem.Restart Windows Update service
You can try restarting Windows Update service and then rename few files if you still get stuck on welcome screen Windows 10 issue.
Here are the steps:
Step 1. Open command prompt.
Step 2. Type net stop wuauserv in the run dialogue and press Enter.
Step 3. Type cd %systemroot% command and press Enter.
Step 4. Type ren SoftwareDistribution SD.old and press Enter.
Step 5. Type net start wuauserv and press Enter.
Step 6. Type exit and press Enter to close Command Prompt and restart your PC.
Step 7. Now, reboot your PC/laptop and check if the stuck on welcome screen has gone.
Restore Windows by using System Restore
System Restore is a useful feature that allows you to restore your operating system to a previous state and fixes any boot problems such as Windows 10 freezes on startup, Windows 7 hangs on welcome screen, etc.
I own a RaspberryPi that I can connect only through ssh. A few days ago it was unsafely powered off. Now when I turn it on I cannot access it. It looks like it turns on but can't get an ip or so.
It is ptovided by fixed IP from router, and when I try to ping this IP, it tells me that the destination host is unreachable.
Is there a way to find out what has happened or the only way is to complete reinstall the OS?
One possibility is that the systems rootfs has been corrupted, this happened to me once with unsafe powerdown on a raspi.
If you have another sd-card, the easiest would be to install a fresh image on it and check if it boots correctly. If not, make an image of your current sd-card, format and reinstall.
Hopefully you've got backups, as there's no guarantee to recover your files if the data has been corrupted.
I've set up raspbian "wheezy" (more information here, and image file here) on my recently arrived raspberry-pi (model B, but with 256MB RAM). Since I plan to use it via SSH from other locations, I was looking for a way to lock the console on the actual machine.
Raspbian is the first unix based OS I am working with, so I'm not really familiar with it, but I think I am looking for something like "vlock".
I installed vlock like this:
apt-get install vlock
When I now log into my pi via SSH from my Windows PC vlock works just fine, but when I try using it on the machine itself it shows a strange behaviour.
If I enter a wrong password, I get the usual message:
vlock: Authentication failure
but immediately after that the commandline shows up as if I entered the right one. So basically everyone can just roll his or her head over my keyboard to unlock my pi.
Does anyone know if this is a known bug (or even intended)? Or are there any equivalents to vlock that I could try?
Thanks in advance.
PS: This is my first question on stackoverflow so I hope I provided enough information. If I didn't, feel free to comment/ask.
We have a VB.NET applciation that is run from a mapped network drive. This works fine on all PCs expect those with Windows 7, on those we get the following:
"application generated an exception that cannot be handled" System.Security.SecurityException was unhandled
If the application folder is copied locally and run from there it works fine.
Anyone know a way aroudn this issue? I assume it is related to Windows 7 netowrk security but not sure how to work around it.
Well, normally you should get this error on all PCs, not only on your Win7 PCs. But I guess for your older Windows PCs someone has solved this issue some time ago. Read this article
http://thebackroomtech.com/2009/04/01/using-caspolexe-to-grant-net-applications-rights-to-a-remote-network-share/
how to deal with the problem. Here is an SO post
.NET Deployment to Network Share
which might help you, too.
There is a reason this error comes up, It is not a good idea to grant applications access to network shares just to run them.
.Net and Click Once makes it very easy to deploy an application to a network share and distribute it to all the client computers to be run from there.
The app can then check for updates whenever it is launched and download any changes. You get all the ease of deploying to a shared drive without mucking about with code access security policies and potentially leaving a nasty hole in your network security.