I installed HP sound driver yesterday and it BSOD-ed my windows and crashed it. System repair didn't help. system restore is corrupted, and startup recovery just says ""patch is preventing windows from starting". when I try to boot, it loads up to certain amount of time and then in just BSOD-s to 0x0000007b.
I disabled the new driver in registry, but it didn't help.
I then installed another windows copy on a new partition, and tried copying over the registry and system32\drivers folder, still the same issue.
Any further ideas? if I could somehow just use the files from system restore that are not corrupted, and leave the rest out, that would help but I don't know how to do that.
Reinstallation was the only way to go unfortunately. I tried replacing windows files, reintegrating registry.. nothing gave stable results. This is not a solution, as I was trying to fix the computer, not reinstall OS.
Related
For reasons unknown yet, my MobaXterm Local Terminal will not start any more on Windows 7 box. There is not even a single error prompt of why this may be happening. I am still able to ssh into remote hosts. Could someone please suggest how to turn on logging in MobaXterm of all its events etc. so that I can debug this break?
Alternatively any explanation on why only the MobaXterm Local Terminal may not start in the application would also be very much appreciated.
Thank you very much for your help.
So the workaround for now is to revert to a previous version of MobaXterm (agree.. not the best solution).
-- Uninstalled MobaXterm 9.1
-- Reinstalled MobaXterm 8.6
Not necessarily we need to move to an old revision. I hope we can take any latest stable branches (not installer) portable edition, and use it.
If this works, there was something goofed up in the installer folder.
This portable edition can be continued, for same configuration and other settings, copy and paste the MobaXterm.ini file from your old location and check if that restores all your settings or crashes.
If this crash, this is day clear of the reason, else we have the old favourite restored.
I just recently upgraded to Windows 10 and ever since I have upgraded I can't get into VB6. I keep getting the System Registry error. I have googled and tried about everything and nothing seems to work. Running VB6 as Administrator is not an option, don't ask but we can't have admin to our computers we have to be logged in as users. The way we use to fix it was to trick Windows 7 log on as Admin run VB6 as Admin then switch me back to user and it worked, but this no longer works. Does anyone have any suggestions that currently have VB6 working as a user and not admin? I really don't want to resort to have to run it out of my virtual machine :( Thanks in advance!
Amanda,
I know it is 3 years later and I wonder what you did. and my solution may be late.
I moved VB6 Enterprise to a Windows10 machine, I did not upgrade the machine to Win10 with the IDE. However to make it work for some of my clients with Win10 machines I:
Back up all the VB6 files, folder and directories.
Using control panel in Win10, uninstall VB6 app. That's right, uninstall!
Using the original install disk, running it as an Administrator, install the program.
If the program has been updated to a later version, you need to get a copy of the latest version and copy over the one that was installed.
Or, Sweet Talk your IT guy into making you a new install disk with the latest version you are supposed to be running.
Go to the folder where the exe file is installed, Right Click on it and open the Properties, and go to the Compatibility tab.
Choose run as an administrator, and also click the Run this program in compatibility mode for Windows XP Service Pack3, or if it shows Latest version of Windows XP try that. You may need to check with your IT department.
Warning: if the VB6 program uses any non-Microsoft tools you may need to register them by hand.
I suspect this has already been worked out for you, but I put it here for anyone that may stumble across it, needing it.
I want to reinstall OS X Yosemite in my MacBook Pro 2015 without erasing the disk. What will I need to reinstall after the process is done? What files are not removed from my hard drive? What files ARE removed from disk?
Thanks!
Run a backup to save all of your data via Time Machine.
Reinstall OSX.
Restore your data from Time Machine if its not available after reinstall.
Run Disk Utility and have the application search and fix any permissions issues that will almost certainly occur when doing a reinstall with applications pulled from a previous install.
DON'T attempt to do a reinstall without making a backup via Time Machine to an external drive.
From #bmike:
"Almost nothing is actually removed. What happens is the installer downloads a fresh and complete set of system files - basically the things that came with the Mac out of the factory minus some iLife apps like Garageband for instance.
The installer doesn't delete any user settings, user files and doesn't even delete apps you installed.
The process is designed to make the system work whether or not you have large or small changes to the system."
Link
I can't start applications from a network share or drive. An error Appears saying that the application was unable to start 0xc0000006. If I copy the .exe on my desktop it works fine.
I tried to start Windows in safe mode and it works too.
My machine run on an HP laptop core i5 with Windows 7 SP1.
Any idea?
EDIT:
I found my problem: It's a bug that append sometimes with Kaspersky endpoint Security v.10. I just uninstall this version and install an older version (v.8). I hate Kaspersky...
Hope it will help someone!
0xc0000006 is an NTSTATUS code. Specifically it is STATUS_IN_PAGE_ERROR.
It is not uncommon to see these errors when you attempt to run an executable from a network volume. For whatever reason, if there is any even intermittent problem accessing the network volume, then you may see this error. When a module is loaded, the code is not physically loaded until it is needed. A memory mapped file is created, and when a particular page is needed, it is brought into physical memory on demand. If your network fails to meet this demand, your application stops with STATUS_IN_PAGE_ERROR.
The common ways to deal with this include:
Getting a more robust connection to your network volumes.
Copying the executable file to a local drive and running it from there.
Adding the IMAGE_FILE_NET_RUN_FROM_SWAP flag to your PE file options.
Thank you for your replies.
I solved the problem by uninstalling Kaspersky end point 10.
My colleges have the version 10 of kasperky and it works but not for me.
I will install an older version waiting for kaspersky v 11.
I'm fairly new to deploying desktop applications, so this is the first time I'm building an installer for my software. Currently, the first time I run my software after installing it, it crashes. After that, it runs fine. I'm still in the process of debugging this issue, but I've noticed that a reboot immediately after installing and before running the software seems to fix this crash.
What are common reasons that some installers ask you to reboot before running the software?
Also, why do some installers need to restart before finishing the installation?
Thanks in advance!
Generally, reboots between install and running are because you're replacing system DLLs that are locked. The installer sets up a run-once registry entry that copies the DLLs during boot before they're locked by Windows, and then your application can use the new DLL that you laid down.
In general, this is highly discouraged. There should be no reason anymore for anyone other than Windows itself to need to reboot after install anymore.
I'd suggest going back into a debugger to find out more details about why your application is crashing. Hopefully you have enough tracing available in your code to allow that type of debugging.
In general, a reboot is only required if the installer needs to replace files that are currently in use (and locked) by the OS. Sometimes installers will err on the side of reboot-just-in-case, but this is rarer than it used to be.
We've got a case with an installer I maintain where we need to force a reboot for vista only due to UAC and privilege elevation. Once the setup is complete we need to trigger a program as the current user context, not the elevated Vista context.
In your case, I suspect that some files haven't been correctly registered and you just need to stick with the debugging ;)