I want to make a Windows store application using the monogame libraries, but for this purpose, I need to install Windows 8.1. The installation fails and gives me the error
0xC1900101 - 0x40017
This error is quite large and alot of people have had or still have it. I made alot of research on it and it seems that this problem is caused by driver incompatibility. I tried the installation about 15 times now, every time updating some drivers, installing updates, etc.
On the installation, it stops at 84% on "Applying PC parameters" step.
So I believe that the problem is that one of my drivers in incompatible and I need to remove it so here are my specs/peripherals:
ASUS G75VW qs71 laptop (16GB RAM, i7 ivy bridge) (I don't think it is the problem, since my friend has the same and it worked for him)
- Logitech G930 Gaming Headset
- Razer Orochi Mouse (Not the 2013, but the 2012)
If some of these drivers are incompatible, please tell me how to remove them.
Thank you.
P.S. I'm not sure if this question is relevant for this site, but it is somewhat programming related and I need it to do programmation.
Related
I am trying to install the CUDA toolkit in order to be able to use Thundersvm in my personal computer.
However I keep getting the following message in the GUI installer:
"You already have a newer version of the NVIDIA Frameview SDK installed"
I read in the CUDA forums that this most probably results from having installed Geforce Experience (which I have installed). So I tried removing it from the Programs and Features windows panel. However I still got the error, so my guess is that the "Nvidia Corporation" folder was not removed.
In the same question, they also suggested performing a custom install. However I could not find any information on how to do a custom install of the CUDA toolkit. I would really appreciate if someone could explain how to do this custom install or safely remove the previous drivers. I thought of using DDU but I read that sometimes it may actually lead to trouble.
I had the same problem while I was trying to get TensorFlow to use my NVIDIA GTX1070 GPU for calculations. Here's what allowed me to perform the CUDA Toolkit installation on my Windows 10 machine.
As the error message in the installer says - you already have a newer Frameview SDK installed. It was the case for me.
Go to Settings/Uninstall or modify programs.
Remove the NVIDIA Frameview program. It should be there with GeForce Experience, PhysX, etc.
Uninstalling only this NVIDIA program didn't cause any driver problems for my machine and I was able to progress through the CUDA Toolkit installation.
I just met the same problem and fixed it now.
This problem occurred because you chose the default installation configuration, which might contain many installed parts. In my situation, I have installed NVIDIA Nsight Compute, which is the culprit during the first few installs.
Unchecking the redundant parts should be helpful.
I have a HP Pavilion dv6 which ran the x32 version of Windows 10, and so I wanted to install x64 OS. Also just a small side-note, the computer was set-up with Windows Insider. Anyway, I also have a Mac, which I created a USB boot drive with x64 Win10 (I originally used the Windows Media Creation software on my dv6), but whenever I tried to open the setup.exe file my dv6 would just say that the software is not compatible. That lead me to think that maybe Windows Insider was having an impact on the OS being slightly newer and not exactly compatible with the setup file... so I stopped Windows Insider updates and rollbacked to the latest Windows. But nope, the file still complained that it wasn't compatible. Skip past 2 days worth of me trying to create a boot drive and booting up my HP, whenever trying to boot up my dv6 with the image loaded on manually or by using Unetbootin, my dv6 would only complain that it's a Non-system disk or the USB drive doesn't contain an operating system.
Simply, I would just like to update my dv6 which now (sorry, I forgot to mention this earlier) after rollbacking now gets stuck in a loop of the green screen of death or blue screen of death and then "Recovering your computer" or something like that, from x32 to x64 os (and yes, I checked that it was capable of running x64 software).
Thanks,
Avoxel284
p.s. this is my first question, so sorry if I sound like some kind of noob or something...
p.s.s. i backed up my files, so all I need is to at least get it to some sort of OS.
I want to positively identify a process that is blocking AMD-V.
Background:
Despite my efforts to resist, Windows 10 decided it was time to upgrade to 1903 and this has left VirtualBox 6.0 inoperable.
(VERR_NEM_MISSING_KERNEL_API).
AMD-V is not available (VERR_SVM_NO_SVM).
I know that is somewhat misleading because:
It worked before.
It is still enabled in the BIOS (I double-checked).
and
I have checked that Hyper-V is indeed still not enabled (Windows 10 Pro). A previous update through me for a loop when it magically turned on, but this time, it doesn't seem to be the culprit.
I don't think it's a zero-day issue because the update has been out for a while. Just for giggles, I decided to press on forward and install all available updates. Still no joy.
I'm starting to suspect that something is using the hardware virtualization and locking the resource. But what? And, how to find out?
Is there a way to identify a running process that is using AMD-V? (Phenom II X6 1055T)
No joy from Googling - I only found heaps of articles repeating the steps above.
Any help would be greatly appreciated. This is probably my last stop before I revert the update.
Thanks!
What helps me:
I installed updates to Windows 10.
I downloaded last Virtual Box (6.0.16)
Turn Windows features on or off
Disable Hyper V, Windows Hypervisor Platform (may be I shouldn`t and last versions are enough.)
tl;dr: Device driver written in NuMega DriverStudio for Win95 to be upgraded to Win10 64-bit. What's the easiest path?
We have a very old product line, which is still selling well. One dll, accessing a UART in a way normal serial handlers can not (to support an even older protocol for another company's products), was made back when the product was first released - for Windows 98! Ever since, it has been working flawless (on 32-bit machines). Therefore, the code has never been touched since it's initial creation!! (This is based on the memory of a few of my colleagues who were around at the time). The only source I have been able to find is from 2001, although one file dates back to 1998.
The driver type is WDM
Now Microsoft have stopped providing 32-bit versions of Windows 10, and customers have started asking for a 64-bit version of our software, so I landed the task of figuring out how easiest to fix it - and support win7 through to Win10, 64-bit.
However the DriverStudio from NuMega was discontinued shortly after the company was purchased by Compuware (and they have lost all knowledge of it!), and even if we were able to find an old version (latest is from 2002), it's unlikely that it's going to help us very much.
I've been searching the web, but haven't found anything giving any suggestions to what the then users of DriverStudio did to upgrade their drivers.
At the time, Jungo WinDriver were an alternative that most people didn't consider to use for 'real' drivers, but perhaps times have changed?
Any advice on how to upgrade this driver code as easy as possible will be highly appreciated.
I've been using ArcGIS 10.1 on my MacBook Pro (2011 model) via Boot Camp for a few months. A few days ago, I just installed Parallels 9 in order to use ArcGIS and my Mac programs at the same time and I've run into an issue with the license needing to be repaired. When I try to open ArcMap via Parallels, I get an error message saying something to the effect of "the license is in need of repair". When I installed Parallels 9, I chose to import my Boot Camp so I didn't have to reinstall anything. My guess is that ArcGIS thinks Parallels is a different computer and that's why the license is failing? Any ideas on how to resolve this issue? I can get a hold of another ArcGIS license so if it's a matter of using another license, I should be ok. Thanks.
You can not use ArcGIS on Bootcamp and VM with the same license key (single use license! - concurrenct use license with separat license server of course no problem). The license key is generated with some internal ids of your computer (eg ethernet MAC and other - you can match the ethernet MAC id in Parallels but thats not enough). You have to chose where you want to work with ArcGIS: bootcamp or VM (before licensing). Thats really annoying...
I had the same issue. Extremely annoying since it is without a doubt impossible to run both your BootCamp and VM versions at the same time. I never resolved it with traditional fixer.
If you are a student (hopefully you are) usually the person/department in charge of license distribution understand the need for both (rasters can be very sluggish on the VM side, but not always) when you are really putting the machine to the test.
SO, that is how i ultimately "solved" the issue. However, I believe the route issue to be the MAC address authentication, as I am experiencing the same problem in ArcGIS 10.2 when I tried to copy my VM from my MBP optical drive to my MBP sad - none of my tools are working.
When I first loaded the copied VM (by opening the VM file directly, not through Parallels) I was prompted if I wanted to use the same "......" (can't remember the actual term, but something along the lines of MAC id, or network address, etc.). Unfortunately I said no make a new one - WRONG ANSWER.
I'm trying to get it sorted now - just saved VM file, completely wiped Parallels, reboot, reinstall; and now I'm on the message boards trying to get this install right) [helpful ideal VM settings for ArcGIS specifically: http://maps.uky.edu/support/docs/BP_ArcGIS_on_Macv5.pdf ).
All that being said the first time I had this issue (month of nightmares, and late GIS homework) I had imported my VM from Bootcamp, which seems logical, but at that time (Parallels 8 and ArcGIS 10) it was still a license error I was receiving, but for some unremembered reason I was convinced it was because the VM calls its hard drive the "C" drive which it clearly is not - parallels merely translates this virtual C drive between the 2 OSs and their respective boot drives.
( I have not tried this next part yet) it might be worth trying to install your VM on the Mac side and then use the Windows or Parallels Migration Tool to create a Win migration file and then go to your BootCamp side (IMPORTANT - DEACTIVATE YOUR ESRI LICENSE BEFORE UNINSTALLING ARCGIS - if you don't do then you'll be mired in the "this license has reached its maximum allowable installations" or whatever they say).
If your Bootcamp side still has your ArcGIS, deactivate, then uninstall that version. Then try to import your migration file, but I've lost some of my Windows skills since switching to Mac, so I would do some research on that part. In theory since, your VM version was pointing to (for all intents and purposes) your "C" drive on the Mac side, hopefully the BootCamp install won't get as tripped up by the double installs as the VM did.
Just a thought, I realize as I finish this that you posted in October, so likely you've moved on, but if any of what I said is wrong, or if you found the best way to have it all, I would really appreciate your response.