I decided to update Windows 8 to 8.1 over the weekend. However after the 4GB download and the 1 hour install procedure, it reverts back to 8 and gives me a message saying that it could not be done.
(the computer works fine still, but in 8.0)
Is this a known issue? How can i find out what the actual reason is? (event viewer was useless)
edited to add:
In this case, the system is a fairly fresh install (2 months and very little use) and has all updates applied. System spec is an i7 920 running stock speed, 2x geforce 260 in SLI, 6GB DDR3.
Your system may be changed in the way that updater fails to recognize some parameters needed.
You may use sfc /scannow to set your OS to the initial state and try updating, but i would recommend to reinstall it completely instead of updating
Related
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.)
I recently got an update (macOS High Sierra 10.13.5 Update), and it seems to have messed with the display a bit.
I use Octave (v4.2.2) to run experiments off of my laptop (MacBook Pro 13-inch, 2.3 GHz Intel Core i5), which requires me to put images on the screen (Psychtoolbox v3.0.14). Since I updated my computer the script errors out at the point where I attempt to put anything on the screen. Unfortunately, because of a bug with Octave, I can't see an error message, so I don't know the exact nature of the problem.
Apart for this problem with Octave, the screen randomly switches to "static" (like the old school TVs!). This only lasts for half a second before it switches back. But I can't help but wonder if both problems have a common root.
Any help is greatly appreciated!
Mrinmayi
I am trying to work out the least disruptive way of beginning to experiment with Windows 8 development. I currently have a Windows 7 Ultimate PC (plenty of disk space, RAM and i7 CPU), and I have a copy of Windows 8 (not 8.1).
I have considered various options:
Convert my whole machine to Windows 8. (Not ideal right now, as I am in the middle of other work, but I may have to do this eventually).
Dual boot Windows 7 & 8. (Can't get this to work. Windows 7 is already installed, and though I can get Windows 8 to install on the second HD, I can't get its boot menu to see Windows 7. I suspect this would be easier if I installed Windows 8 first, but that would be a huge pain.)
Run either OS using a virtual machine. (I haven't looked into this yet, and I have no idea what is involved.)
As a final option, I wondered if it is possible to develop Windows 8 applications on a Windows 7 PC and remote debug on an attached Windows 8 device? (I'd prefer to do this, as it is a way I have worked often in the past while doing console development.)
Does anyone have any experience of any of this - positive or negative? It takes ages to experiment with this stuff, with the constant threat of recking my existing work environment. I'd really appreciate any advice or pointers to articles that deal with any of this stuff.
Microsoft do their loyal developers no favours. I've paid hundreds for modern hardware, Windows versions and Visual Studio, and still it seems difficult to say the least to develop for their latest OS.
Kind wishes ~ Patrick
Option 4 is not possible. In similar situation I went with option 2 and gratually migrate myself completly to windows 8.
If you have problems with boot try to ask on superuser.com or better search the web for guideline.
If you want to develop applications for Windows 8 don't go with option 3.Please see this post on installing Visual studio in VM.
Regarding option 2,verbatim from Microsoft
You must install the older operating system first, and then install the more recent operating system. If you don't (for example, if you install Windows Vista on a computer already running Windows 7), you can render your system inoperable. This can happen because earlier versions of Windows don't recognize the startup files used in more recent versions of Windows and can overwrite them.
But as #Antonio said there may be roundabout for option 2.
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.