Registry editor on a virtual machine
I am running a very basic small business setup using a 2012 Server to host a Windows 2008r2 Virtual machine on. The only reason I'm hosting an older VM is because of some legacy software that is not supported on a later OS. Anyway, I need to edit the registry
on the 2008 server for this legacy software and I can't get the editor to run. I get no error messages when trying to launch either regedit or regedit32. Any ideas?
Thanks
Sorry Moka5, I reposted in the server blog. Thanks for answering. I can get a cmd prompt just fine and when I type in the regedit command it simply flashes back to the main desktop. Nothing is running in services or under programs on task mgr either. Interesting.
Similar Messages
-
Hi,
I am running BPA on My Exchange 2010 VM (Server 2008 R2 VM on Hyper-V) and get the following errors:
The 'Services' string type value located in 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\Setup\Services' registry key is missing or inaccessible. The Microsoft Exchange Information Store service won't start. As a result, all services that depend
on this service won't be able to start
Exchange server [Exchange Server FQDN] is a virtual machine but the additional tools are not installed. This configuration is not supported. Install Virtual Machine Additions for this guest.
Problem is that, for the first, that Key exists and the service is actually running fine. And for the second my VM tools are already installed.
Hopefully someone out there has had the same issue and can assist.
PeteHi Pete,
For the first error message, please try the following steps:
Make sure the Information Store service is in Starting status,
Automatic startup type and works well, as a test we can try to
restart the Infroamtion Store service and verify the service works well.
Start
Registry Editor, find the registry key “Services” under “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\Setup”, its value is “C:\Program
files\Microsoft\Exchange Server\v14”(default install location), please check your registry, make sure the key “Services” exist and value is the Exchange Server install location and the
location is accessible;
Start
Registry Editor, and locate the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Setup
Use the
Permission option under the Security tab to check the permission setting on this key. Make sure
System is in the list with Full Control permissions if the service account is Local System. If you are not using Local System as the service account, check the existence of the corresponding account in the list and ensure that
it has Full Control permissions. Please refer to this article:
Title: Exchange Store Does Not Start: Errors 7024, 1026, 9542, and 5000
Link:
http://support.microsoft.com/kb/285116
Start
ADSI Edit, and then browse to the following location:
Domain.com/Configuration/Services/Microsoft Exchange/Org/Administrative Groups/AdminGroup/Servers/Server Name
Right-click the
server name, and then click Properties.
Click the
Security tab, make sure this own server’s server object have
full control permission on its own server.
If not or the object is missing, please modify the permission or click
Add, locate the computer account for the Exchange Server computer, add it to the Permissions list with full control.
Click OK, and then close ADSI Edit.
Use
Active Directory Users and Computers to add the current affected
Exchange Server computer account to the Exchange Servers(previous version should be “Exchange Domain Servers”) group in the
Microsoft Exchange Security Groups( or Users) OU. Refer to this article:
http://support.microsoft.com/kb/297295.
Restart the Exchange Server computer, then rerun the ExBPA.
For the second error message, Microsoft don’t recommend to install Exchange Server on virtual machine without additional tools, so the error message occurs. We can just ignore
this message, it will not affect the Exchange servers.
Regards, Eric Zou -
Install R12 on a Virtual Machine hosted on Windows Vista
I wanted to install Oracle EBS R12.1.1 on Windows Vista Home Premium 64-bit but used to get .\jre\nt\1.6.0\bin\java error. Hussein Sawwan
helped and said that this is not certified. He adviced me to create a VMWare Server. Following is my experience. I hope it is helpful. Any
suggestions, additions are more than welcome. Thanks to all who helpmed me especially Hussein Sawwan, Helios, Gareth Roberts.
I used to get .\jre\nt\1.6.0\bin\java error after the installation would zoom through 33%. That was because my staging area was not correct. The staging area should be just next to c:\ or whatever be the root directory (or drive). No space or special characters in folder name. My current structure is as follows:
c:\r12stage. Under r12stage I have following folders and subfolders
oraAppDB -- 49 Disks
oraApps -- 11 Disks
oraAS -- 3 Disks (This comes from the Rapid Install Tools)
oraDB -- 5 Disks
startCD -- 1 Disk plus other folders. Just copy startcd from the unzipped download and paste to r12stage area.
I then created a virtual machine using VMWare Server (free download but need to register to get the serial number). Because I installed
vmware server on Vista Home Premium 64 bit Host OS, I have to boot my machine by pressing F8 and then select Disable Digital Signature
Enformcement. Thanks to Gareth Roberts for this tip. Create a vm and install Windows 2003 by selecting the .img file (first cd) by selecting Use ISO image and then path of the windows 2003 cd 1 (zipped file). start the virtual machine, that will install windows 2003 and then ask for location of 2nd cd. On the host machine, where the second win 2003 zip file resides, unzip the second zip file and name the folder as cd2. share this folder to the __vmware_user__ and from the virtual machine, map network drive to \\hostmachinename\cd2. Select this as the location of cd2 and complete the installation. Install MKS Toolkit from http://cygwin.com/ and visual c++ from Microsoft website. for information on this please refer to the following URL. Thanks to Muhammad Habib
http://mhabib.wordpress.com/2007/03/14/installing-oracle-applications-e-bussiness-11i-on-windows-xp/
After installation is done and Windows Update is run, share the r12stage directory on the host machine to the vmuser and launch rapidwiz.cmd from the command prompt and follow the instruction. For internet connection from the VM use Ethernet as NAT.
If the installation errors halfway through, clean up your VM by following instructions in document id 292424.1 in MetaLink. If you dont have access to Metalink then I summarize the steps briefly over here.
Launch the Registry Editor.
Navigate to the HKEY_LOCAL_MACHINE\Software key.
Select the Apache Group subkey and delete it.
Select the Oracle subkey and delete it.
Navigate to the HKEY_LOCAL_MACHINE\System\Current Control Set\Services.
Carefully select and delete each service beginning with Oracle. For example, delete "Oracle Apache Server PROD_<nodename>".
When you are finished, exit the Registry Editor.
Navigate to the Environment Variables editing screen according to your system setup. For example, right-click My Computer and select
Properties. From the Advanced tab, click the Environment Variables button.
Select the following system variables if created during the failed installation, and delete them: DISCO_JRE, DISCO_VBROKER, JSERV,
VBROKER_JAVAVM, VBROKER_TAG, WV_GATEWAY.
Select the Path variable, but do not delete it. Carefully edit it and remove any component with "Oracle" in the name, or that otherwise
references the failed install. For example, delete "E:\11.5.10\test\visora\8.0.6\bin;".
Save and exit System Properties.
Open a command window and navigate to the C:\Program Files\ directory. Delete the Oracle subdirectory.
If your Oracle Inventory directory was not C:\Program Files\Oracle\Inventory and was therefore not deleted in the previous step, locate it
and delete it.
Restart your machine
It is now safe to remove the Oracle filesystem that was partially installed during the failed installation. Go to the base install directory,
or top-level directory under which you installed either the Database Server (DATA, DB) or the Applications Tier Server (APPL, ORA, COMN)
directories, or both. Note that you may choose to rename a directory before you delete it. This allows you to use the same directory name and start a new installation even before you finish the delete filesystem operation. For example, if you placed your filesystem in a "test" directory under
"E:\11.5.10":
C:\> E:
E:\> cd 11.5.10
E:\> rename test oldtest
E:\> del /s /q oldtest
In another window:
C:\> cd <stage install directory>
Q:\> rapidwiz.cmd
After cleaning up if you still get error like RW-50004: Error Code received when running external process. Check log file for
details. Running database Install driver for VIS instance, after 13% complte step 1 of 5 then I suggest that you re-create the machine and follow the above steps again. Including installing win 2003, mks tool kit , vc++, etc. It will be a success.
Starting concurrent manager takes up enormous memory and slows down everything, so if you dont need it then dont ever start it. APPS password is apps and sysadmin user is sysadmin.
Good luck.
Mahesh AcharyaI had Vista 64-bit machine, installed Ubuntu in VMWare. Installed Oracle apps on 32-bit Ubuntu under VMware and was able to access Oracle apps. But, it is very very slow. It hangs sometimes and takes 15-20mins to display Ubuntu screens. Am I missing something here. I have a 4GB RAM and VMWare can not use all the 4GB. It may be using 2GB of 4GB. Am I missing something?
-
Hi there,
just wanted to share my experience with a manual P2V Migration. The VM became to ressource hungry and it was decided to move it off an ESX 5 Cluster to a dedicated physical Machine.
V2P Virtual Machine to physical Server IBM x3650 M4 and switch from BIOS to UEFI Boot environment
Task:
V2P Migrate a VMware virtual machine to a IBM x3650 M4 with a ServeRAID 5110e RAID Controller or any other LSI RAID Controller without 3rd Party tools.
This should also work with other RAID Controllers or Servers but be sure to pick the right drivers then.
Extra Task:
The VM's boot environment/virtual BIOS is BIOS, not UEFI (as per default VMware Setting). The physical Server is running in UEFI mode.
The Challenge:
After restore the Server won't boot or get into a BSOD (7B), because the RAID drivers are missing.
After restore the VM won't boot because the boot environment has changed from BIOS to UEFI
Preparations:
An existing physical Server of the same type and with the same RAID controller and same OS would be nice for troubleshooting and checking the registry.
An existing DHCP server will make networking things easier.
Connect the new physical server x3650 M4 to power and network
create a virtual drive that has at least the size of the existing VM plus the size of the full backup (.vhd). Should be about twice the size of the original vmdk.
Get a USB Flash stick (I used a 8GB modell so no problem with larger sticks)
Download and extract LSI MegaRAID Driver on that USB media (I used 6.705.05.00-MR_Windows_Driver directly from LSI website)
Download and extract INTEL Network Adapter Driver on that USB media (I used 12.11.97.0 of e1r62x64.inf from 19.5 driver release from 2014.09.26 directly from LSI website)
Step by Step:
if you have an other physical Server of the same type and same Controller and same OS:
1. open regedit and export everything related to SCSIAdapter and megasas2 to .reg files or skip this step and use my files below
some of this (sub)keys may not be accesible - you will then first take ownership and/or modify permissions to read them
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1000&DEV_005B&SUBSYS_04121014&REV_05
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\megasas2
this one is more complicated:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase (only relevant are those devices where the service name is megasas2 - export the whole subkey and get the filtering done with tools like notepad++)
Make a copy of the following files/folders:
c:\programdata\LSI\
c:\windows\inf\megasas2.INF
c:\windows\inf\megasas2.PNF
c:\windows\system32\drivers\megasas2.SYS
on the existing VM:
1. create a full backup (image) with the built-in Windows Backup Utility and save it in an accessible network location (you will need this one, if anything goes wrong or you want to come back to this point.
Alternatively you could create a VMware snapshot.
2. import the .reg files you created earlier or import my files below.
Attention: This will make the VM unbootable!
But it is required to prepare the VM for the new RAID controller when it will be restored on the physical server.
Do NOT reboot now as this will make the VM unbootable!
4. Copy the LSI folder and the megasas2.INF/PNF/SYS files to the appropriate destination folders on the VM.
3. again create a full backup (image) with the built-in Windows Backup Utility and save it in an other accessible network location but not where you safed the first backup.
This will be the "golden" backup if you want, where the RAID controller is prepares. We will rebuild the new machine with this second backup.
4. Optional: you could use the Backuputility now to restore the Systemstate of the first backup and reboot or restore the VMware snapshot.
This will undo the changes we made to the VM.
on the new physical server:
1. boot the physical server from Windows Server 2008 R2 SP1 DVD
2. when it is ready to install, press shift+F10 to get command prompt and do not click to install Server 2008
3. check driveletter of the USB stick with diskpart list vol (was C: at my Server, so don't wonder about that letter)
3. load drivers for ServeRAID SAS controller (this is mandatory to see the volume in diskpart)
drvload c:\srv_2008_x64\megasas2.inf
4. load drivers for INTEL I350 Gigabit NIC's (you will need this to access the backup that is on the network)
drvload c:\PRO1000\NDIS62\e1r62x64.inf
5. wpeinit (will start network. wait ~15 sec to let it start and get IP address)
check if you have IP connectivity an address with ipconfig, if not, use an other NIC driver and repeat steps 4+5
6. create the EFI and BCD
diskpart
list disk
select disk x (where x is the number of the disk to convert)
clean
convert gpt
create partition EFI size=128
format fs=fat32 quick label=EFI
assign letter=i or any other free drive letter
create partition MSR size=128
6.1 Copy EFI bootloader to EFI partition
i: (where i is the letter of your EFI partition)
mkdir EFI\Boot
mkdir EFI\Microsoft\Boot
copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Microsoft\Boot (where x ist the default letter of the current Windows PE environment)
copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Boot\bootx64.efi (note that the file will be renamed to bootx64.efi)
7. create the new partitions
diskpart
create partition primary size=100000 (edit the size to your needs. this will later become the system drive of your server)
format fs=ntfs quick label=Windows
assign letter=Y or any other free drive letter
create partition primary size=990000 (this will temporarily store your backup and we need it for the restore process)
format fs=ntfs quick label=Backup
assign letter=B or any other free drive letter
exit
8. map network drive and copy the backup .vhd to the local disk
net use L: \\networklocation\where\you\saved\the\backup (enter the credentials when asked)
copy the .vhd file that contains the OS of your VM to the local Backup Partition B. The relevant vhd file is usually the largest file in that fileset.
Note that the names are very similarly - be sure to get the correct file!
copy "L:\WindowsImageBackup\VMNAME\Backup 2015-02-03 123456\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd" B:\
give it time, this is slow and will take some minutes/hours and you will not see any progress! Look at the disk-LED's to see if anything is still happening
9. mount the .vhd and copy it's contents to the new system partition
Note that you can only mount a locally stored .vhd. You cannot mount a .vhd in a network location.
diskpart
select vdisk file=B:\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd
attach vdisk
select vol 5 (where 5 is the number of the mounted vdisk)
assign letter=Z or any other free drive letter
exit
10. Restore the files from the image
z: (where z is the letter of your mounted .vhd)
xcopy * Y:\ /e /c /h /k /o /b /q /y (where Y: is the letter of your new partition with the label "Windows")
several "Access denied" messages appear, ignore them. Those are SystemVolumeInformation folders.
11. Create Boot Configuration Data (BCD)
bootrec /RebuildBcd
this will try to repair the missing BCD on the second of the two small partitions we created earlier in and should normally work, otherwise you'll have to create BCD manually (search google for that procedure)
Note that it may find more than one Windows installation and ask which sould be added to the boot list. Be sure to select only the one that is in the correct Volume (Y:\)
that's it - exit the DOS command box and close the "Install Windows" Window, after a prompt it will reboot.
Select "Start Windows Normally", if Windows Error Recovery appears.
12. Preparing Windows
When Windows boots for the first time, DO NOT reboot if you are asked, it won't come back at this stage!
Install Intel chipset drivers for the Server (I used "intc_dd_inteldp_9.4.0.1026_windows_32-64.exe" from IBM website)
Open Device Manager, uninstall the "RAID-Controller" with the exclamation mark. You cannot install the correct driver for this Device at this point, it will bring you the error: "Cannot create a stable subkey under a volatile
parent key"
Once again, DO NOT reboot!
In Device Manager select Action>Add Legacy Hardware
click Next
select Hardware manually
select Storage Controller as Type
LSI should be listed, select "LSI MegaRAID SAS 9281-8E"
click Next, ignore the error "Code 10" Message.
Click Done.
Rightclick the LSI MegaRAID SAS 9281-8E device with the exclamation mark in Device Manager
select Update driver
select Browse my computer for driver software
select let me pick from a list of device drivers on my computer
select "Have Disk"
browse to the folder where the extracted RAID driver 6.705.05.00-MR_Windows_Driver is located (e.g. USB Flash stick E:\6.705.05.00-MR_Windows_Driver\srv_2008_x64)
then unselect "Show Compatible Hardware"
on the right side, scroll up and select "IBM ServeRAID M5110e SAS/SSATA Controller"
ignore the Update Driver Warning and click Yes
click Next, ignore the error "Code 10" Message.
ignore the exclamation mark on "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager but be sure that there is only this controller and no other RAID-Controller or LSI SAS Controller listed under "Other Devices"
or "Storage Controllers"
NOW you are safe to reboot
After reboot you will find two "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager
Rightclick and uninstall the one with the exclamation mark. Do not tick the checkbox to remove the driver as well!
You're done!! (hopefully)Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C31115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C38015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C41115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C48015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C51115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C58015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C61115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C68015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C71115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C78015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C81115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C88015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C91115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C98015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20219E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20319E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0071&SUBSYS_00721137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00011BD4]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00721137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00731137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_008F1137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B01137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B11137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B61137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B71137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C21137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C31137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_03B11014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040D1014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_10541000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_11771734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_14581002]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_1F201462]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_30351054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350C8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350D8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_822910F1]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_843B1043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_84711043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92211000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92401000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92408086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92411000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92418086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92421000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92431000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92441000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A01000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A11000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92501000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92511000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92701000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00011BAA]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00021BD4]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00791137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_02001AE3]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B21014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B31014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03C71014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_070015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11761734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11B31734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_30361054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_350B8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84731043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84801043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_8985152D]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92551000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92561000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92568086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92601000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92608086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92611000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92618086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92621000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92631000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92641000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92648086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92671000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92678086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92681000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92688086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92751000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92758086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92761000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92768086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92771000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92801000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92808086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92811000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92821000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92828086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92841000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92881000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92891000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92901000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92908086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20819E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20919E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0409&SUBSYS_10091000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10011000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10018086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10021000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10031000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10038086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10041000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10081000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10088086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100C1000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100D1000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10811734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10a31734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20041000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20051000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_30161054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_34908086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35008086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35018086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35048086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35078086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_82871033]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0413&SUBSYS_10051000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7" -
Virtual PC - Create new virtual machine snap in button not appearing
I was asked to move this question here so here it goes...
I have installed virtual PC and have the XP mode image working on Win 7 64 bit on a Dell Optiplex 990 i5. However when I choose the Windows Virtual PC manager and the Windows explorer window opens, I don't see the create virtual machine option, just
'burn' where it should be. How do I get the snap in option to appear to create a virtual drive? The window appears with the title Virtual Machines.
I have tried enabling the windows 7 aero UI thinking the classic windows appearance was somehow blocking this but that had no effect.
I tried re-installing the virtual pc setup directly from the website but it give me the message that it's isn't suitable for use. I tried un-installed and re-installing but get the same where the explorer window is missing the snap in.
Again, the XP mode image works properly and starts and shuts down without any issues.Below is the fix for the virtual machines folder for WinVPC when the folder
here “%username%virtual machines” is missing the
“Create Virtual Machine” option.
Making changes to the Registry is potentially dangerous, always have a backup before proceeding.
The fix is pretty simple, copy and paste the following lines into notepad and save
to a *.reg file, then double-click to run it (you shouldn’t need to reboot for
the fix to take effect, close and re-open the window:
Windows Registry Editor Version 5.00
[-HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\BagMRU]
[-HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Bags]
[-HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\BagMRU]
[-HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\Shell\Bags]
[-HKEY_CURRENT_USER\Software\Classes\Local
Settings\Software\Microsoft\Windows\Shell\BagMRU]
[-HKEY_CURRENT_USER\Software\Classes\Local
Settings\Software\Microsoft\Windows\Shell\Bags] -
I have installed two virtual machines(win2k3 32bit and win2k3 64bit ) on Windows Server 2008 RC1 With Hyper-V Technologies (Beta) enterprise. Mouse is getting lost inside VM (using CTRL+ ATL + LEFT ARROW comes mouse control control in host OS).
Is there any setting to make mouse works? Insert Integration Serice setup Disk operation succeeds.all credits for mike_something
The problem is that the old mousedriver is hooked to the mouse device class.
To remove this dependency, go into the registry and navigate to the key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96F-E325-11CE-BFC1-08002BE10318}
Remove the value msvmmouf from the UpperFilters Regvalue.
Reboot....
tadaaa!!
If you wish you can take out the drivers completely by deleting these registry hives completely :
The driver:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\msvmmouf
The Service:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\VPCMap
The CopyHook Shell Extension: ( for folder access )
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{30C14BA C-122C-42ED-B319-1139DBF48EB8}\InProcServer32
HKEY_CLASSES_ROOT\Directory\shellex\CopyHookHandle rs\VPCCopyHook
After a reboot you can delete the "Virtual Machine Additions" folder from program files...
Good Luck! -
Hello,
I have a asp.net mvc 5 web application running on .net 4.5 hosted on my local windows 8 machine on macbook pro using parallels. I'm running Internet Explorer 8 Version: 8.0.6001.18702 running on XP and Version: 8.0.7601.17514 running on Windows 7 Enterprise.
I've got both of the virtual machine source from www.modern.ie
My web application is attempting to provide single page user experience by having some client-side routing by using '#!/xxx' hashbangs in the url so that I can get and post via ajax and change the hash in the url without causing the page to reload. My
code works fine in IE9+ and other modern browsers.
However, I'm facing this strange issue in both of the IE8 versions. When running my demo app in IE8, I can login, view home page and can navigate from this home page to many details page. From the very first login page, all the pages are the result
of form's post action via ajax which then expects html from server and loads in the DOM. The page structure of my app is like summary form => Details page (can also contain summary forms) => Details...so on.
The above process works fine for few of the navigation steps. If I keep navigating from one page to another & go back, I have observed that the browser back button is removing the history items slowly. And a time comes when it totally forgets about
all the history pages that I visited to reach this current page I'm viewing!! It treats like I have just started my browsing session and this current page is the first page I've landed on with no back option. Now if I again try to navigate, I have encountered
problems like both the back and forward buttons gets disabled.
Hope, my words above is clear enough to explain this problem. The same application works fine in IE9+ and other browsers.
Till now, I have tried following steps on both VMs:
Resetting IE8.
Increasing disk space to 1024mb for temporary internet files storage.
Setting 'Never' for Check for newer versions of stored pages.
Disabling the automatic crash recovery feature didn't helped in this case. Found this on support website.
Deleted temporary files, history, cache, etc many a times.
Search many forums, posted question on StackOverflow, ASP.NET
Forums - but didn't helped.
Tried 'beforeunload' event of browser to see if any of the page is reloading because of submit or any other reason. But the page doesn't reload at all.
The issue is browser forgets about the browsing history while I'm still browsing the same site.
Is there any possible fix for the issue above? Does IE8 have any issues as many ajax form post is happening on every page?I have really tried many things to identify any possible reason of the issue above. Even rewrote all my javascript navigation code and checked server-side code.
But the only place where I got the solution is at site: http://www.enhanceie.com/ie/bugs.asp which states that there is a bug in IE8 which reads like:
IE0012: IE Travellog broken when navigating back/away from a page with
a large POST form If there is a form input field with a value longer
than 523,659 characters, when you navigate away from the page, IE may
clear the current session's travellog (similar to history), disabling
the back and forward buttons. Repros in IE6 & IE7.
There are following solutions that you can go for:
- Check for the input field that has lots of characters as mentioned above and solve your problem.
- If you have control over the system where IE8 will be used, you can add the following registry key on that machine. There is no existing key, so, you need to add a new one:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\TravelLog] "MaxSize"=dword:ffffffff
I am really relaxed to find this information as I spent really long time to solve this issue. Hope this will help someone. -
Host: Windows Server 2012 R2 with Hyper-V and RRAS (for Internet over NAT)
VM: Windows Server 2012 R2 with installed Active Directory Domain Services
When I open AD DS configuration window (“promote this server to a domain controller”) many services and programs on my host (include Hyper-V, RRAS & Server Manager) fails with RPC Server unavailable error.Hello Aleksandr,
There wasn't any configuration information, ipconfig /all, network setup, etc. So it's difficult to tell.
More importantly, are you trying to promote the host server? If yes, that is not advised, for one, because it's a Hyper-V server, (not suggested at all), and two, RRAS is installed. RRAS is problematic with any domain controller because it turns it into
a multihomed domain controller.
Active Directory communication fails on multihomed domain controllers
http://support.microsoft.com/kb/272294/
Multihomed DCs (with more than one unteamed NIC or multiple IPs) with DNS, RRAS, iSCSI, Clustering interfaces, management interfaces, backup interfaces, and/or PPPoE adapters - A multihomed DC is not a recommended configuration, however there are ways to
configure a DC with registry mods:
http://blogs.msmvps.com/acefekay/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters/
7 Reasons not to Make Hyper-V a Domain Controller
http://www.altaro.com/hyper-v/reasons-not-to-make-hyper-v-a-domain-controller/
Domain Controller as Hyper-V host
https://social.technet.microsoft.com/Forums/windowsserver/en-US/4ff14bec-a815-473b-8d2a-33e91e17197b/domain-controller-as-hyperv-host?forum=winserverhyperv
Networking?
I don't know how your networking is setup, whether there are multiple NICs on the host server, if they are teamed, if you have the host interface set to allow the operating system to share administration, or if there are separate interfaces for each. Can
the host OS ping/communicate with the DC virtual machine?
If there are more than one NIC, you have the choice to team the NICs and share the Teamed NICs for the Hyper-V OS and the VMs, or keep them separate where one is devoted for the Hyper-V OS, and one for the VMs.
Hyper-V Server VLAN Network Configuration
https://social.technet.microsoft.com/Forums/windowsserver/en-US/0aa71d2a-ebf9-4a3e-bbf5-94db55339fa2/hyperv-server-vlan-network-configuration?forum=winserverhyperv
Recommendation:
Why not just create another VM DC?
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights. -
We have a problem with one of our deployments of Windows Server 2012 Hyper-V with a 2 node cluster connected to a iSCSI SAN.
Our setup:
Hosts - Both run Windows Server 2012 Standard and are clustered.
HP ProLiant G7, 24 GB RAM. This is the primary host and normaly all VMs run on this host.
HP ProLiant G5, 20 GB RAM. This is the secondary host that and is intended to be used in case of failure of the primary host.
We have no antivirus on the hosts and the scheduled ShadowCopy (previous version of files) is switched off.
iSCSI SAN:
QNAP NAS TS-869 Pro, 8 INTEL SSDSA2CW160G3 160 GB i a RAID 5 with a Host Spare. 2 Teamed NIC.
Switch:
DLINK DGS-1210-16 - Both the network cards of the Hosts that are dedicated to the Storage and the Storage itself are connected to the same switch and nothing else is connected to this switch.
Virtual Machines:
3 Windows Server 2012 Standard - 1 DC, 1 FileServer, 1 Application Server.
1 Windows Server 2008 Standard Exchange Server.
All VMs are using dynamic disks (as recommended by Microsoft).
Updates
We have applied the most resent updates to the Hosts, VMs and iSCSI SAN about 3 weeks ago with no change in our problem and we continually update the setup.
Normal operation:
Normally this setup works just fine and we see no real difference in speed in startup, file copy and processing speed in LoB applications of this setup compared to a single host with two 10000 RPM Disks. Normal network speed is 10-200 Mbit, but occasionally
we see speeds up to 400 Mbit/s of combined read/write for instance during file repair.
Our Problem:
Our problem is that for some reason a random VHDX gets copied to System Volume Information by "System" of the Clusterd Shared Storage (i.e. C:\ClusterStorage\Volume1\System Volume Information).
All VMs stops responding or responds very slowly during this copy process and you can for instance not send CTRL-ALT-DEL to a VM in the Hyper-V console, or for instance start task manager when already logged in.
This happens at random and not every day and different VHDX files from different VMs gets copied each time. Some time it happens during daytime wich causes a lot of problems, especially when a 200 GB file gets copied (which take a lot of time).
What it is not:
We thought that this was connected to the backup, but the backup had finished 3 hours before the last time this happended and the backup never uses any of the files in System Volume Information so it is not the backup.
An observation:
When this happend today I switched on ShadowCopy (previous files) and set it to only to use 320 MB of storage and then the Copy Process stopped and the virtual Machines started responding again. This could be unrelated since there is no way to see
how much of the VHDX that is left to be copied, so it might have been finished at the same time as I enabled ShadowCopy (previos files).
Our question:
Why is a VHDX copied to System Volume Information when scheduled ShadowCopy (previous version of files) is switched off? As far as I know, nothing should be copied to this folder when this functionis switched off?
List of VSS Writers:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {7848396d-00b1-47cd-8ba9-769b7ce402d2}
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {8b6c534a-18dd-4fff-b14e-1d4aebd1db74}
State: [5] Waiting for completion
Last error: No error
Writer name: 'Cluster Shared Volume VSS Writer'
Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
Writer Instance Id: {d46c6a69-8b4a-4307-afcf-ca3611c7f680}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {fc530484-71db-48c3-af5f-ef398070373e}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {3792e26e-c0d0-4901-b799-2e8d9ffe2085}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {6ea65f92-e3fd-4a23-9e5f-b23de43bc756}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {71dc7876-2089-472c-8fed-4b8862037528}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {cb0c7fd8-1f5c-41bb-b2cc-82fabbdc466e}
State: [1] Stable
Last error: No error
Writer name: 'Cluster Database'
Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
Writer Instance Id: {23320f7e-f165-409d-8456-5d7d8fbaefed}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {f23d0208-e569-48b0-ad30-1addb1a044af}
State: [1] Stable
Last error: No error
Please note:
Please only answer our question and do not offer any general optimization tips that do not directly adress the issue! We want the problem to go away, not to finish a bit faster!Hallo Lawrence!
Thankyou for youre reply, some comments to help you and others who read this thread:
First of all, we use Windows Server 2012 and the VHDX as I wrote in the headline and in the text in my post. We have not had this problem in similar setups with Windows Server 2008 R2, so the problem seem to be introduced in Windows Server 2012.
These posts that you refer to seem to be outdated and/or do not apply to our configuration:
The post about Dynamic Disks:
http://technet.microsoft.com/en-us/library/ee941151(v=WS.10).aspx is only a recommendation for Windows Server 2008 R2 and the VHD format. Dynamic VHDX is indeed recommended by Microsoft when using Windows Server 2012 (please look in the optimization guide
for Windows Server 2012).
Infact, if we use fixed VHDX then we would have a bigger problem since fixed VHDX are generaly larger then Dynamic Disks, i.e. more data would be copied and that would take longer time = the VMs would be unresponsive for a longer time.
The post "What's the deal with the System Volume Information folder"
http://blogs.msdn.com/b/oldnewthing/archive/2003/11/20/55764.aspx is for Windows XP / Windows Server 2003 and some things has changed since then. for instance In Windows Server 2012, Shadow Copies cannot be controlled by going to Control panel -> System.
Instead you right-click on a Drive (i.e. a Volume, for instance the C drive/Volume) in Computer and then click "Configure Shadow Copies".
Windows Server 2008 R2 Backup problem
http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/0fc53adb-477d-425b-8c99-ad006e132336 - This post is about the Antivirus software trying to scan files used during backup that exists in the System Volume Information folder and we do not
have any antivirus software installed on our hosts as I stated in my post.
Comment that might help us:
So according to “System Volume Information” definition, the operation you mentioned is Volume Shadow Copy. Check event viewer to find Volume Shadow Copy related event logs and post them.
Why?
Furhter investigation suggests that a volume shadow copy is somehow created even though the Schedule for Shadows Copies is turned off for all drives. This happens at random and we have not found any pattern. Yesterday this operation took almost all available
disk space (over 200 GB), but all the disk space was released when I turned on scheduled Shadow Copies for the CSV.
I therefore draw these conclusions:
The CSV Volume has about 600 GB of disk space and since Volume Shadows Copy used 200 GB, or about 33% of the disk space, and the default limit is 10% then I conclude that for some reason the unscheduled Volume Shadow Copy did not have any limit (or ignored
the limit).
When I turned on the Schedule I also change the limit to the minimum amount which is 320 MB and this is probably what released the disk space. That is, the unscheduled Volume Shadow Copy operation was aborted and it adhered to the limit and deleted the
Volume Shadow Copy it had taken.
I have also set the limit for Volume Shadow Copies for all other volumes to 320 MB by using the "Configure Shadow Copies" Window that you open by right clicking on a drive (volume) in Computer and then selecting "Configure Shadow Copies...".
It is important to note that setting a limit for Shadow Copy Storage, and disabaling the Schedule are two different things! It is possible to have unlimited storage for Shadow Copies when the Schedule is disabled, however I do not know if this was the case
Before I enabled Shadow Copies on the CSV since I did not look for this.
I now have defined a limit for Shadow Copy Storage to 320 MB on all drives and then no VHDX should be copied to System Volume Information since they are all larger than 320 MB.
Does this sound about right or am I drawing the wrong conclusions?
Limits for Shadow Copies:
Below we list the limits for our two hosts:
"Primary Host":
C:\>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Shadow Copy Storage association
For volume: (\\?\Volume{e3ad7feb-178b-11e2-93e8-806e6f6e6963}\)\\?\Volume{e3ad7feb-178b-11e2-93e8-806e6f6e6963}\
Shadow Copy Storage volume: (\\?\Volume{e3ad7feb-178b-11e2-93e8-806e6f6e6963}\)\\?\Volume{e3ad7feb-178b-11e2-93e8-806e6f6e6963}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: 320 MB (91%)
Shadow Copy Storage association
For volume: (E:)\\?\Volume{dc0a177b-ab03-44c2-8ff6-499b29c3d5cc}\
Shadow Copy Storage volume: (E:)\\?\Volume{dc0a177b-ab03-44c2-8ff6-499b29c3d5cc}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: 320 MB (0%)
Shadow Copy Storage association
For volume: (G:)\\?\Volume{f58dc334-17be-11e2-93ee-9c8e991b7c20}\
Shadow Copy Storage volume: (G:)\\?\Volume{f58dc334-17be-11e2-93ee-9c8e991b7c20}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: 320 MB (3%)
Shadow Copy Storage association
For volume: (C:)\\?\Volume{e3ad7fec-178b-11e2-93e8-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{e3ad7fec-178b-11e2-93e8-806e6f6e6963}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: 320 MB (0%)
C:\>cd \ClusterStorage\Volume1
Secondary host:
C:\>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Shadow Copy Storage association
For volume: (\\?\Volume{b2951138-f01e-11e1-93e8-806e6f6e6963}\)\\?\Volume{b2951138-f01e-11e1-93e8-806e6f6e6963}\
Shadow Copy Storage volume: (\\?\Volume{b2951138-f01e-11e1-93e8-806e6f6e6963}\)\\?\Volume{b2951138-f01e-11e1-93e8-806e6f6e6963}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: 35,0 MB (10%)
Shadow Copy Storage association
For volume: (D:)\\?\Volume{5228437e-9a01-4690-bc40-1df85a0e6736}\
Shadow Copy Storage volume: (D:)\\?\Volume{5228437e-9a01-4690-bc40-1df85a0e6736}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: 27,3 GB (10%)
Shadow Copy Storage association
For volume: (C:)\\?\Volume{b2951139-f01e-11e1-93e8-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{b2951139-f01e-11e1-93e8-806e6f6e6963}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: 6,80 GB (10%)
C:\>
There is something strange about the limits on the Secondary host!
I have not in any way changed the settings on the Secondary host and as you can see, the Secondary host has a maximum limit of only 35 MB storage on the CSV, but it also shows that this is 10% of the Volume. This is clearly not the case since 10% if 600
GB = 60 GB!
The question is, why does it by default set a too small limit (i.e. < 320 MB) on the CSV and is this the cause of the problem? I.e. is the limit ignored since it is smaller than the smallest amount you can provide using the GUI?
Is the default 35 MB maximum Shadow Copy limit a bug, or is there any logical reason for setting a limit that according to the GUI is too small? -
Could not initialize the Java Virtual Machine
While trying to configure the turnkey product I encounter an error in starting the JBoss for Adobe LiveCycle ES v8.0 service. The JBossService.exe ends up showing in the task list - but the service shows its status as "starting" and an enty stating: "Could not initialize the Java Virtual Machine" is placed in the event log. I've seen a posting on this form that traced at least some of these symptoms to the account under which the service is configured to run - but I don't believe that solution applies in this case - I'm starting the service under the System Account which has all the permissions it needs to start the service.
Thanks very much for the suggestion. Indeed, the problem turned out to be memory related - I was able to correct the issue by updating the registry keys "JVM Option Number 4" and "JVM Option Number 5" so specify lower values. For some reason the system didn't like the 1024 meg size that was set by default (our server has 2 gig of memory).
-
IP Virtualization not working in Virtual Machine on Hyper-V
Hello everyone. Have such issue. We are using cisco agent desktop for our users. For working in Terminal server environment it needs dedicated IP for each program session. Currently we'are using hardware server with Windows Server 2008 R2 SP1 with RDS.
We've added IPpool in registry for Virtualisation per program. It works fine. Now i'm trying to create a virtual machine with WS 2012 R2 with the same configuration(Hyper-V 2012 R2). The problem is it doesn't work. When creating new session or launching new
program i get APIPA address or get nothing at all. Will it work or still this functionality doesn't work?have you setup the IP virtualization GPOs in the new environment?
computer configuration > administrative templates > windows components > remote desktop services > remote desktop session host > application compatibility
I'm not sure what regkeys you have implemented but you may want to see if they still apply to 2012 R2, you might have to remove them -
No pdf printer in mac - so No pdf printer available in 'virtual machine' on the mac-any suggestions?
I am running Mac OS X version 10.6.2 and I installed CS4 on the laptop. I have Acrobat 9 Pro - and no pdf 'printer' due to Mac's new operating system. Unfortunately, I also have a virtual machine on my laptop running Windows XP (with VMWare Fusion). I need the 'pdf printer' in my virtual machine to create pdf's from my Windows programs. When I bought the Mac version of CS4 (including Acrobat) I didn't know the 'printer' wasn't included and I can't see buying another Acrobat for Windows....does anyone have any suggestions for installing the pdf printer so my virtual machine has access to the printer?
Hey, guys! be careful, there's a sneaky catch with this "no-pdf-printer" thing.
The warning, concerns mostly the pros (publishers, editors, typographers....) who are used in CMYK chromatic gamut.
The catch is this: you get a CMYK archive, all right, but the color tone IS COMPLETELY DIFFERENT than the one you were used to get with the old good method. That's because, when you choose the "save as adobe pdf" option, initially you get an RGB CONVENTIONAL arch (check the "colors" tag: there 's no CONVENTIONAL CMYK option available). Of course, if you choose to Distill it so that your final arch is a PDF CMYK, what you finally get IS a CMYK archive, BUT: THE COLOR TONE IS TOTALLY DIFFERENT! The Reds are pretty much down, and there's a green-ish cast upon it.
What you can do (and this could be an answer to the dear friend with the difficult onscreen name) is this:
You can install a virtual PPD PRINTER (an LPD). If you Google "virtual ppd printer for OS 10.6" you get the directions, DIRECTLY from Adobe (anyhow, the link is http://kb2.adobe.com/cps/404/kb404931.html).
And... VOI LA! You can use this (choosing as a PPD Device the "GENERAL IMAGESETTER") in order to make things the good old way (print it as a PS and after DISTILL it enjoyably!!!).
I wonder, why Apple want to make our lives difficult, pretending the same moment that it only makes them easier...
Well, it's pretty much understandable: SNOW LEOPARD is the "prova generalle" before LION is unleashed. They test us, they weigh us, they are watching our reactions, thus validating for FREE their products. They are clever! but being clever just by considering the others (and treat them) as if they were fools, IS NOT HONEST AT ALL!
Got it Stevie? -
How to connect the two virtual machine .
I installed VM workstation and created two virtual machine .Please suggest me how to connect them internally each other though vm network editor.I want create RAC Setup for practice.
NAT is the default adapter type in VirtualBox, which will work in almost any configuration and networking environment. Using the NAT adapter, the host system will establish connections on behalf of the guest OS. NAT requires that the corresponding VM guest adapter uses DHCP and cannot be used to provide any services unless you configure port forwarding (>1024) at the VirtualBox VM NAT adapter.
Bridged networking is the most transparent adapter type, but requires a physical network adapter on the host OS, which is limited depending on the host system and hardware, e.g. wireless. It also requires that the user understands network and routing restrictions of the host system in case of using the interface to communicate between the host and VM. A combination of host-only and NAT may sometimes be necessary to allow the VM to connect to the internet and allow the host to communicate with the VM guest OS.
Btw, the host-only adapter IP actually works on behalf of the host OS and can be used to allow the VM to access the host system. So if Internet is not required, the NAT or bridged adapter are not required. I'm not sure if many people realize that, since it's not really mentioned in the documentation. So if you use the host-only adapter, simply use the host-only IP instead of the host system real IP to connect the VM to the host OS.
I also switched to VirtualBox a couple of years ago, mainly because it provides more VM hardware options, is free and because of the ability to manage multiple virtual machines and group them together. I have about 70 virtual machines for testing and evaluating configured on my home computer. I also like the option in VirtualBox to clone a VM based on a Snapshot.
VMware provides a Virtual Network Editor in VMware Workstation (KB 1018697), which allows to customize any of the existing virtual network adapter or add new ones. The available technologies under any Type 2 hypervisor are very similar between different products:
http://www.vmware.com/support/ws45/doc/network_configure_ws.html -
Hello,
I downloaded Java Runtime Environment v1.4.0_01
on my C drive in a windows folder. When I try to run it,
it says that my security settings need to be set to medium.
I set it to medium and hit apply then refresh as I'm supposed to do.
But each time it says I need to set it at medium again.
The real problem is I'm trying to set up a webpage on Homestead.com
& I got started but needed a virtual machine so I downloaded the above software from Sun.com But everytime I click on the Homestead icon to ( open up )return to build my page it says : "Error : Microsoft Virtual Machine not found Class registry error".
Can any of you help me please ?
Thanks,
Robertu know sun has filed a case law one against Microsoft
in regarding this virtual machine...
best thing u do is go to microsoft site and downlaod
a Microsoft's Java Virtual Machine...
and install it
thats it... -
"Could not create Java virtual machine" for several XP SP3 clients
Hi,
In this last year I got the message "could not create java virtual machine",
(suddenly, after several mounths without any kind of problem),
on 10-15 XP SP3 clients in our lan, lan in which all the 200 clients (90% XP SP3)
have this application installed.
Every time the solution seems to be different:
sometimes the cause is a virus, sometimes i have to disinstall all Java components
and reinstall only the Java RE 6.0_23 (used by the application),
sometimes I have to make also a system registry cleaning for Java components,
only few times was enough to clear the Java cash, change the kind of Java network connection,
delete the temporary files...
In two situations the problem was solved changing UltraVnc with RealVnc
and only once the user solved himself restarting the computer...
I'd like to know which is the meaning of this message and which steps is better
to follow in order to solve the problem in the shortest time.
Thank YouThank you
for anwering my question !
Anyway, in all the 10-15 cases I solved this problem, I hadn't to change the amount of RAM...
never... and, once solved, the computer client is ok and the application works without subsequent problems...
So, as I said, i can solve the problem without Knowing the real reason, and often after several
hours... (you can read in my previous comment about a lot of differences solutions...)
The matter is... that I can't understand "how and why" I solve the problem...
Bye
Maybe you are looking for
-
Finder sidebar not updating with applications open/save dialog boxes
Hi all, I've searched the threads and can't seem to find an answer to this recurring issue that I'm having. I save folders to current projects in the Finder sidebar. However, I find that when I try to find those sidebar folders from within the open/s
-
Custom Fields in BSEG not updating on FI document post
Hello Experts I'm facing a problem when posting FI documents. I'm using BAPI_ACC_DOCUMENT_POST and passing some Z fields using Table Extension2 (bapiparex). The problem is that the Z fields are not getting updated. BADI_ACC_DOCUMENT is implemented an
-
What is the best cooling pad for a MacBook Pro 13in?
What is the best cooling pad for a MacBook Pro 13 inch?
-
Isolate linksys router from LAN while retaining internet
Hi guys, got a bit of a problem that I've spent the past 3 hours trying to nail down. My main router is a MI424WR for my FIOS connection. It serves several computers, wired and wireless. I have an old linksys BEFW11S4 router that I am trying to use w
-
Adobe Web Site and Live Chat do not work
Most pages on the adobe support site give me the Jboss error message 413 Header Length too Large I missed the phone support deadline by 15 minutes and the live chat support doesn't work either. Anyone else having these issues?