Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

An internal virtual machine error (192) has occurred.

333 views
Skip to first unread message

Adrian Esdaile

unread,
Oct 4, 2007, 9:10:01 AM10/4/07
to
I've been using VPC for legacy apps for some years now, and it has all been
working very well.

I've just made the jump to Vista Ultimate, and installed VPC2007. It seems
that it does not like my old Windows 98 vhd though, as it boots into win98,
and just as the desktop appears the following error box pops up

"An internal virtual machine error (192) has occurred. The virtual machine
will reset"

The error box is occuring at the Vista-OS level, not the W98 level - the
error is 'outside' the VPC as far as I can tell.

My hunch it that it's mouse related - it seems to be occuring just as the
mouse pointer should appear in W98.

I can still access my files in that vhd of course, but I can't run the W98
environment.

(and what am I doing? testing web pages made by my partner in various old
OSes - I even keep ancient W95 and NT4 images - oh the nostalgia!)

Robert Comer

unread,
Oct 4, 2007, 9:27:08 AM10/4/07
to
There's a couple of things you can try, one being to turn of HW
Virtualization for that VM and see if that makes any difference, and
the other is to try boot into safe mode and uninstall the VPC
additions, then reboot and reinstall the VPC additions.

--
Bob Comer <Microsoft MVP Windows - Virtual Machine>

Adrian Esdaile

unread,
Oct 5, 2007, 12:45:01 AM10/5/07
to

> There's a couple of things you can try, one being to turn of HW
> Virtualization for that VM and see if that makes any difference, and
> the other is to try boot into safe mode and uninstall the VPC
> additions, then reboot and reinstall the VPC additions.
>
> --
> Bob Comer <Microsoft MVP Windows - Virtual Machine>

I'm not running HW Virtualization, or at least I don't think I am - that
selection box is greyed out.

By 'boot into safe mode' do you mean safe mode in the host OS or safe mode
in the virtual os?

Although now I come to type it - that's probably the answer. So.. F8 when
booting into the virtual W98, then remove what is likely to be the VPC
additions for VPC2005... yeah, that makes sense, will try it over the weekend
and post the response.

Benjamin Armstrong [MSFT]

unread,
Oct 6, 2007, 2:24:09 PM10/6/07
to
Is there any chance that you can try creating a new Windows 98 virtual
machine and seeing if the problem reproduces (you can certainly keep
your current one around while trying this out).

Cheers,
Benjamin Armstrong
============================
Windows Virtualization Program Manager
Blog: http://blogs.msdn.com/Virtual_PC_Guy
Book: http://tinyurl.com/ysxcbm

This posting is provided "AS IS" with no warranties, and confers no
rights. You assume all risk for your use.

Adam Dudley

unread,
Apr 25, 2008, 10:25:58 AM4/25/08
to

Hitting F8 on Win98 boot, then unistall additions, then reinstall additions in normal mode fixes the problem.

Thanks

Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com

Luis Javier

unread,
Oct 30, 2008, 2:05:17 PM10/30/08
to

Ì´m getting a similar problem but in a different way. Lets say i have 2 different laboratories, with same kind of machines. Ñets call them Room A and Room B. Just trying to start an already created virtual machine in both.

In the PC's of room A , im getting that error - (192) -

In room B, where the machines should be equal, the virtual machine works fine.

I´m using Virtual PC 2007 in both places.

Any idea would be useful, thanks in advance.

Robert Miles

unread,
Oct 31, 2008, 2:37:47 AM10/31/08
to

"Luis Javier" <ljgarr...@ikasle.ehu.es> wrote in message
news:2b2405b6-8a90-4a5f...@text.giganews.com...
Are both of you running all your virtual machines on an operating system
with the same bit size as the older machine? Some virtual machine
programs have problems running virtual machines of a different bit
size than the CPU the virtual machine program is running on, or
not providing most of the instructions the simulated machine requires.


Javier@discussions.microsoft.com Luis Javier

unread,
Nov 5, 2008, 10:18:01 AM11/5/08
to
The problem is that, in my case, both places use the exact same machines,
identical OS etc. What im looking for is something that could cause a VM to
crash in a machine but not in another. I just havent any clue. Brain totally
empty of ideas right now.

Bob Campbell

unread,
Nov 5, 2008, 3:05:58 PM11/5/08
to
"Luis Javier" <Luis Jav...@discussions.microsoft.com> wrote in message
news:47127B02-1111-4B1C...@microsoft.com...

> The problem is that, in my case, both places use the exact same machines,
> identical OS etc. What im looking for is something that could cause a VM
> to
> crash in a machine but not in another. I just havent any clue. Brain
> totally
> empty of ideas right now.

The only time I've had problems like this is when I copied the VHD and the
VMC file to another computer. In my experience, it is better to just copy
the VHD (hard disk) file to the new machine, then create a new VM using the
wizard. Presumably you end up with the same VMC file, but if there is the
slightest difference between the host machines you can have problems when
trying to use a VMC file created on another machine.

Just my 2 cents.

Luis Javier

unread,
Nov 6, 2008, 10:41:01 AM11/6/08
to
Ok, really werd, after ensuring the 2 machines are identical, tried to create
a new VMC. Did it identical to the ona i had (who works in the other
identical machines). I failed again. But when disabling the Hardware
Virtualizacion, it is working now. really strange as said, but OK, i hope it
can help others.

Thx you all a lot for the help.

sachapo...@gmail.com

unread,
Apr 16, 2017, 4:36:44 PM4/16/17
to
Good Evening fellow friends..

I had the same error 192, re installed host OS to solve, didnt work, I disabled hardware virtualisation on the Windows 7 VM, didnt work, I went into my BIOS and disabled VT Technology and it solved the problem! My symptoms were the same, 1 VM would run on 1 PC but not another. Hope this saves someone else the 4 hours it took me..
0 new messages