1

I tried to install and get the CS50 Appliance to work on my mini laptop. I am using VirtualBox and my mini laptop is a Canaima MG101A4. The error I receive reads, 

VirtualBox - Error In supR3HardNtChildScrewUpPebForInitialImageEvents
NtWriteVirtualMemory/Peb failed:0xc0000022 (rc=-1073741790)

And once I click on Abort, it shows 

Failed to open session for virtual machine CS50 Appliance 2014. 
The virtual machine 'CS50 Appliance 2014' has terminated 
unexpectedly during startup with exit code 1 (0x1).

I read and tried a bunch of suggestions from this site, but was unsuccessful in resolving the issue. If this isn't fixable, what are my other options?

Improve this question
4
  • 1
    Are you using VMware or VirtualBox? What error is it giving, or what isn't working correctly?
    – Melde
    Jan 13, 2015 at 3:06
  • What is the exact model of your laptop? The other option is to install the CS50 library and other tools manually, but that is much more complicated.
    – Chrisuu
    Jan 13, 2015 at 4:52
  • I am using VirtualBox and my mini laptop is a Canaima MG101A4. The error reads, "VirtualBox - Error In supR3HardNtChildScrewUpPebForInitialImageEvents" "NtWriteVirtualMemory/Peb failed:0xc0000022 (rc=-1073741790)" And once I click on "Abort", Then it shows, "Failed to open sessionfor virtual machine CS50 Appliance 2014. The virtual machine 'CS50 Appliance 2014' has terminated unexpectedly during startup with exit code 1 (0x1)." If this isn't fixable, how can I go about the other option?
    – Brainysol
    Jan 13, 2015 at 10:11
  • I added relevant information from your last comment to your original post. Please note that you can do this yourself in the future by using the edit link underneath the post. Good luck and let us know how it goes.
    – Chrisuu
    Jan 13, 2015 at 20:20

2 Answers 2

Reset to default
0

I do not know if it will work with your machine's hardware, but I was able to get the CS50 Appliance running on my x86 computer using VMWare Player as the hypervisor. I had to use version 6.0.4 since that was the last version that supported x86 processors. And yes, it is free for non-commercial use. It is another option if you want to try to uninstall VirtualBox and start fresh.

Improve this answer
1
  • Awesome! This has solved my problem.
    – Brainysol
    Jan 14, 2015 at 8:48
0

This appears to be a security-related error between Virtual Box and your Windows host. I found a post on the Virtual Box forum made by someone who experienced a very similar error, and he was pointed by a moderator to a subforum containing a massive thread about these issues.

As a first potential fix, users are advised to apply a fix from Microsoft.

If you have a Windows 7 host that started failing in the last few days then this is most likely due to the buggy Windows update KB3004394. Microsoft have released a fix.

The thread also mentions that there might be issues with Comodo and Symantec Endpoint Protection, both of which seem to be security products. Disabling these products temporarily, if you have them, might also be worth a shot.

If the issue isn't fixed, you can follow the instructions in the same thread to post your specific diagnostic data to it, which will be used in determining and hopefully resolving the issue in a future Virtual Box release.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .