Veritas - disabled drives

Hello,
I hope this is the right forum, thanks in advance for any insight. I didn't setup the box and the owner has left me with it. Having some issues with a server that has SAN drives managed with Veritas.
Version is;
#uname -a
SunOS xxx.com 5.9 Generic_118558-06 sun4u sparc SUNW,Sun-Fire-V440
# pkginfo -l VRTSvxvm
   PKGINST: VRTSvxvm
      NAME: VERITAS Volume Manager, Binaries
CATEGORY: system
      ARCH: sparc
   VERSION: 4.1,REV=02.17.2005.21.28
   BASEDIR: /
    VENDOR: VERITAS Software
      DESC: Virtual Disk Subsystem
    PSTAMP: VERITAS-4.1z:2005-02-17
INSTDATE: Jun 28 2005 12:18
   HOTLINE: 800-342-0652
     EMAIL: [email protected]
    STATUS: completely installed
     FILES:      808 installed pathnames
                  19 shared pathnames
                  17 linked files
                  98 directories
                 416 executables
              291031 blocks used (approx)Problem is;
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
Disk_0       auto:sliced     -            -            online
Disk_1       auto:sliced     ROOT_VOL02   ROOT_VOL     online
Disk_2       auto:sliced     ROOT_VOL04   ROOT_VOL     online
Disk_3       auto:sliced     ROOT_VOL01   ROOT_VOL     online
Disk_5       auto:cdsdisk    IMAGES01 IMAGES   online
Disk_6       auto            -            -            error
Disk_7       auto            -            -            error
Disk_8       auto:cdsdisk    DEPT04      DEPT        online
Disk_9       auto            -            -            error
Disk_10      auto            -            -            error
Disk_11      auto            -            -            error
-            -         DEPT01      DEPT        failed was:Disk_10
-            -         DEPT02      DEPT        failed was:Disk_9
-            -         DEPT03      DEPT        failed was:Disk_7
-            -         DEPT05      DEPT        failed was:Disk_11
-            -         IMAGES02 IMAGES   failed was:Disk_6Not a solaris admin, I have familiarity with command line. Thanks again.

rtm'd it, got it going.

Similar Messages

How to disable drive letter assignment for Windows 7 64 bit

Hi everybody,
Currently, I have a problem that need your help for my company
I received a new request from my boss, that is disable USB removeable storage on Windows 7 64 bit
I found out and apply some solutions from internet but it cannot be solved
In some solutions, I pay attention to a good one: Disable drive letter assignment for Windows 7 64 bit
I think it may solve my problem. But how to do it??? I need your help from all of you
Thanks for your support!!!!

Hi,
Let's verify your issue. Did you want to disable USB storage device?
If yes, try this:
1. If you have not ever already done so, you must connect a USB storage device
to the computer now, and wait until Windows installs it and displays it in the Computer window with an assigned drive letter, then
disconnect it.
2. Press the Windows + R keys to open the Run dialog, type
regedit, and press Enter.
3. If prompted by UAC, then click on Yes.
4. In Registry Editor, navigate to the location below:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\USBSTOR
5. In the right pane of USBSTOR, double click on Start to modify it.
6. Type in 4, click on OK.
7. Close Registry Editor windows.
Karen Hu
TechNet Community Support

Windows 7 only gives me active USB ports when the DISABLE DRIVER SIGNATURE ENFORCEMENT is selected during system boot

I can only use the computer if I press 8 and select "DISABLE DRIVER SIGNATURE ENFORCEMENT". Without this, the system comes up OK but I do not have access to the keyboard and mouse. If I select any other boot option the system boots up but I am
unable to login since neither the keyboard nor the mouse is working.
The Device Manager is clean. All drivers work and have digital signatures. I tried to use local group policy editor to disable digital signature enforcement but was not able to make any difference. The OS is 64-bit Windows 7 Professional with Service Pack
1 and latest updates.
The system includes a WD USB 3.0 card, which I have been using for over 3 years without any problem. I recently (3 days ago) updated the WD SmartWare for Windows software. It seems that my problem coincides with this update. Since then, I removed WD SmartWare
and Installation software and restored the Registry to its previous restore point however the problem still exists.
As per SIGVERIF the not signed drivers are:
difxapi.dll              7/13/2009      2.1.0.0          Not Signed
usbccgp.sys              9/4/2013       6.1.7601.18251      Not Signed
usbd.sys                 9/4/2013       6.1.7601.18251      Not Signed
usbehci.sys              9/4/2013       6.1.7601.18251      Not Signed
usbhub.sys               9/4/2013       6.1.7601.18251      Not Signed
usbport.sys              9/4/2013       6.1.7601.18251      Not Signed
usbuhci.sys              9/4/2013       6.1.7601.18251      Not Signed
The problem appears to be related to the not signed USB drivers.
The current USB 3.0 host controller is from Renesas Electronics (ver. 2.1.39.0). According to the Device Manager it is digitally signed and working fine.
Does anyone know how to fix this problem?
Thanks,
DC

This issue was fixed on my PC as follows.
1) Taking ownership of the above usb*.sys files in the drivers folder
2) renaming them to usb*.sysold
3) Using Device Manager to uninstall all USB devices with the yellow warning ! next to them
4) Doing a Scan for Hardware changes via the Device Manager toolbar and then waiting a few moments whilst the USB devices are re-installed with signed drivers.
Hope this helps you....
usb drivers files in my drivers folder after the above process:
12/02/2013 04:12            19,968 usb8023.sys
21/11/2010 03:24            32,896 USBCAMD2.sys
27/11/2013 01:41            99,840 usbccgp.sys
12/07/2013 10:41           100,864 usbcir.sys
27/11/2013 01:41             7,808 usbd.sys
27/11/2013 01:41            53,248 usbehci.sys
25/03/2011 03:29            52,736 usbehci.sysold
27/11/2013 01:41           343,040 usbhub.sys
25/03/2011 03:29           343,040 usbhub.sysold
25/03/2011 03:29            25,600 usbohci.sys
27/11/2013 01:41           325,120 usbport.sys
25/03/2011 03:29           325,120 usbport.sysold
14/07/2009 00:38            25,088 usbprint.sysold
11/03/2011 04:37            91,648 USBSTOR.SYS
25/03/2011 03:29            30,720 usbuhci.sys
21/11/2010 03:23           184,960 usbvideo.sys
              19 File(s)      2,783,104 bytes
The .sysold files are the ones I renamed, I think also renamed the usbccgp.sys - but accidentally deleted it after the rename..

Disable Driver Enforcement for Virtual Audio Cable?

Hi, I'm trying to get this thing called "Virtual Audio Cable" Working, but It is apparently not signed, so I cant even use it. Is there a fix to this? I've tried to use bcdedit -set. I have tried to use DSEO Too, but I dont know what file it wants
me to sign, so I'm confused. So if anyone has any idea what to do with this, it will be very helpful.
(PS, Not really the best with computers. But if you guide me through what you want me to do. It'll be easy.)

Hi,
Do you mean that you're unable to install the unsigned driver for Virtual Audio Cable? If so, you can choose “Disable Driver Signature Enforcement” during boot, this allows unsigned drivers to load for this boot only.
You can refer to workarounds mentioned in blog below
How to install unsigned drivers
http://blogs.msdn.com/b/matthew_van_eerde/archive/2014/04/05/10211068.aspx
And there's a security policy to configure the Unsigned driver installation behavior in previous Windows versions, but removed since Vista
Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Devices: Unsigned driver installation behavior
while you can refer to this KB to re-add this policy option, this KB is for Windows Vista, but I have tested in my Windows 7 enterprise, it also works.
http://support2.microsoft.com/?kbid=947250
Add: as Rick mentioned, Eugene Muzychenko should be more familiar with this product
Yolanda Zhu
TechNet Community Support

Encore WT8 - Disable driver signature enforcement

I need to install a Fiio DAC driver which keeps failing.
Fiio themselves say that I need to disable driver signature enforcement in order to install the driver.
I've followed their instructions with regard to Windows 8.1 but when I get to the final selection screen where I need to press the f7 key, the keyboard is not accessible.
Is there any way around this as without it I will not ba able to use the DAC.
Cheers
Mike

Hi dude
I would recommend you to check if its really possible to install and to use such driver on an Windows tablet. Secondly, the Encore WT8 tablet supports an external keyboard via USB or Bluetooth.
So in case your issue is related to not visible keyboard, I would recommend you to test an external keyboard plugged to the tablet.

HOWTO: Create a Boot Configuration That Has No Driver Signature Checks. Disable Driver Integrity Checks and Install a Custom Non-Signed Driver

Hello,
Recently, I had a task where I needed to install a custom non-signed driver onto my Windows 8 64-bit setup. As it is known, Windows has driver enforcement policies that, as a security measure, do not allow you to install non-signed drivers.
I did not want to alter my current boot configuration so I decided to create a separate boot entry that would have driver signing policies disabled. For some reason I did not find any good source that would contain a step-by-step instruction on completing
this task, so I decided that I'd better share my experience here.
Lastly, there are multiple ways how you could turn off driver enforcement policies, but I find the way to do this via boot manager.
Here's how you can do that.
1. Press WindowsKey and type 'cmd' (without quotes) to find Command prompt, then click Command prompt icon. If you have User Account Control turned on, hold Ctrl+Shift keys pressed when clicking the icon.
This will force Windows to ask you for elevation of command prompt. Elevation is necessary for editing Boot Configuration Database (BCD), the database used by Windows boot manager to store boot settings.
2. In the User Account Control window click Yes to confirm elevation of command shell.
3. At the command prompt type
bcdedit
to list your BCD entries.
This will give you an output like:
Windows Boot Manager
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
{a329b5cc-fb29-11e1-a74d-f2c962d62240}
{a329b5ca-fb29-11e1-a74d-f2c962d62240}
{a329b5c2-fb29-11e1-a74d-f2c962d62240}
{current}
{a329b5d8-fb29-11e1-a74d-f2c962d62240}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
device vhd=[D:]\win8prowmc01.vhdx
path \Windows\system32\winload.efi
description Windows 8
locale en-US
inherit {bootloadersettings}
recoverysequence {a329b5d1-fb29-11e1-a74d-f2c962d62240}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8prowmc01.vhdx
systemroot \Windows
resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
The section that starts with Windows Boot Manager lists current settings for the boot menu. Here you find what boot entry is chosen by default, this is the one what you will boot into if you do not select any boot entry in the
boot menu.
The following record
default {current}
indicates that by default my Windows boots into configuration which I use at the moment (currently booted Windows configuration).
To find out what exactly is current configuration, look into the list of boot entries, records that contain boot loader configuration and are titled as Windows Boot Loader in the bcdedit output.
For example, the entry shown above is one of my boot configurations. This is one of the boot entries listed on the boot manager screen when I start my PC and it looks like:
Windows Boot Loader
identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
device vhd=[D:]\win8prowmc01.vhdx
path \Windows\system32\winload.efi
description Windows 8
locale en-US
inherit {bootloadersettings}
recoverysequence {a329b5d1-fb29-11e1-a74d-f2c962d62240}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8prowmc01.vhdx
systemroot \Windows
resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
This record has a unique GUID identifier that can be used to reference this boot entry, which is:
identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
If we look at the Windows Boot Manager settings, we'll see this entry is the first in order to be displayed in the boot menu on OS start (I marked the unique bits):
displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
{a329b5cc-fb29-11e1-a74d-f2c962d62240}
It references my VHD drive, a virtual hard drive where my Windwos 8 setup is residing:
device vhd=[D:]\win8prowmc01.vhdx
And it also specifies that the boot manager must use UEFI BIOS extension code to access my Windows boot partition:
path \EFI\Microsoft\Boot\bootmgfw.efi
3. Now locate the current boot entry.
Current boot entry contains boot settings used to boot into Windows configuration to which you are currently booted. It is referenced in the list of boot entries as a Windows Boot Loader record that has the {current} keyword inside and may
look like:
Windows Boot Loader
identifier {current}
device vhd=[D:]\win8rtm.vhdx
path \Windows\system32\winload.efi
description Windows 8 Enterprise RTM
locale en-US
inherit {bootloadersettings}
recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8rtm.vhdx
systemroot \Windows
resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
Because we are more than happy with current configuration and want to base our new boot configuration on these settings, we need to copy this boot entry ({current}) to a new boot entry.
This is done by running the following command:
C:\Windows\system32>bcdedit /copy {current} /d "No Driver Signature Check"
Parameter /d here indicates that the following sequence of characters specifies the display name for the new boot entry that we are creating. The name inside the double quotes will be displayed in the boot menu when you boot your Windows.
In other words, if you know restart your system, you'll see the new No Driver Signature Check in the boot menu.
When copied, the entry is automatically given a new GUID identifier, so upon running the command above, you'll see the following line returned (you'll have an other GUID since these are unique identifiers):
The entry was successfully copied to {a329b5d8-fb29-11e1-a74d-f2c962d62240}.
4. Make sure the entry has been successfully created.
Run the same bcdedit. (You may specify /enum or /v, or both /enum /v parameters at the prompt to get more detail about boot entries, but simple bcdedit is just enough to see the new entry):
C:\Windows\system32>bcdedit
Windows Boot Manager
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
{a329b5cc-fb29-11e1-a74d-f2c962d62240}
{a329b5ca-fb29-11e1-a74d-f2c962d62240}
{a329b5c2-fb29-11e1-a74d-f2c962d62240}
{current}
{a329b5d8-fb29-11e1-a74d-f2c962d62240}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
identifier {current}
device vhd=[D:]\win8rtm.vhdx
path \Windows\system32\winload.efi
description Windows 8 Enterprise RTM
locale en-US
inherit {bootloadersettings}
recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8rtm.vhdx
systemroot \Windows
resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
Windows Boot Loader
identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
device vhd=[D:]\win8rtm.vhdx
path \Windows\system32\winload.efi
description No Driver Signature Check
locale en-US
inherit {bootloadersettings}
recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8rtm.vhdx
systemroot \Windows
resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
The entry has been created and given a unique a329b5d8-fb29-11e1-a74d-f2c962d62240 ID. It now has exactly same boot settings as the boot entry we used to boot into current configuration of Windows.
5. Modify created No Driver Signature Check entry and specify that Windows must have driver integrity checks disabled when booted using this boot entry.
Any modifications to boot entries are made using /set parameter. To indicate that we modify a specific boot entry, we must specify the GUID for the No Driver Signature Check record, which is:
identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
In other words, to edit (add or change) an option for the boot entry, we need to use the following command syntax:
C:\Windows\system32>bcdedit /set GUID <boot_option> [<option_value>]
First, we must specify that we don't want integrity checks be made. This is done by adding the loadoptions option and setting it to DISABLE_INTEGRITY_CHECKS value:
C:\Windows\system32>bcdedit /set {a329b5d8-fb29-11e1-a74d-f2c962d62240} loadopti
ons DISABLE_INTEGRITY_CHECKS
The operation completed successfully.
6. Verify that load option has been added.
Run the bcdedit command:
Windows Boot Loader
identifier {current}
device vhd=[D:]\win8rtm.vhdx
path \Windows\system32\winload.efi
description Windows 8 Enterprise RTM
locale en-US
inherit {bootloadersettings}
recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8rtm.vhdx
systemroot \Windows
resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
Windows Boot Loader
identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
device vhd=[D:]\win8rtm.vhdx
path \Windows\system32\winload.efi
description No Driver Signature Check
locale en-US
loadoptions DISABLE_INTEGRITY_CHECKS
inherit {bootloadersettings}
recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8rtm.vhdx
systemroot \Windows
resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
7. Add the option that turns on test signing mode and disables checks of driver signature.
Adding the testsigning option and setting it to ON does the trick for us:
C:\Windows\system32>bcdedit /set {a329b5d8-fb29-11e1-a74d-f2c962d62240} TESTSIGNING ON
8. Now we have a boot entry that enables Windows not to do integrity checks and digital signature validation.
We check it by running bcdedit:
Windows Boot Loader
identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
device vhd=[D:]\win8rtm.vhdx
path \Windows\system32\winload.efi
description No Driver Signature Check
locale en-US
loadoptions DISABLE_INTEGRITY_CHECKS
inherit {bootloadersettings}
recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
integrityservices Enable
recoveryenabled Yes
testsigning Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8rtm.vhdx
systemroot \Windows
resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
9. Type 'exit' without quotes to exit from command prompt, and restart Windows.
Upon booting you will be present with a new boot option to start Windows in configuration that allows you to install custom non-signed drivers.
Hope this will help anybody to create their own custom boot configurations.
Well this is the world we live in And these are the hands we're given...

Hi,
Thank you for sharing the solutions & experience here. It will be very beneficial for other community members who have similar questions.
Regards,
Kelvin hsu
TechNet Community Support

Disabled driver for HD Graphics 4000, now black screen.

I tried to disable HD graphics 4000 so I could use Nvidia NVS 5400M graphics full time, but when I disabled the HD graphics 4000 driver in Device Manager, the screen went black. I tried plugging in a external monitor in the VGA port but nothing happened.
How can I enable this driver again with no screen???
Thanks ahead of time for anyone's help,
Solved!
Go to Solution.

Keep in mind that you are always using the HD 4000 unless an application needs the NVS 5400M, that's how Optimus works. You can force Optimus to be used more by preferring it in the Nvidia control panel.

How can I disable drive mode on S6?

Hi all, excited to have new S6 but the drive mode turns on at random, even when I'm sitting at my desk and phone is stationary. Very annoying for people to get texts saying I'm driving when I'm not driving. The instructions for disabling this feature on S5 and other devices don't seem to hold for S6. Does anyone have similar issues and figured this out? I ended up moving my default message app to Samsung from Verizon as a result.
Thanks,
Tim

timcoates,
Let's get to the bottom of this! How often if this happening? How long has this been going on? Have you tried rebooting the phone? I reviewed the user manual https://ss7.vzw.com/is/content/VerizonWireless/Devices/Samsung/Galaxy%20S6/GalaxyS6_UM_33015.pdf for this phone and do not show this is an available setting on this phone.
JohnB_VZW
Follow us on Twitter @VZWSupport
If my response answered your question please click the "Correct Answer" button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!

How to disable drive upon LabView error

I'm running a closed loop PD position controller in Labview 8.5 and NI PCI-6259 M series card and BNC-2120. I'm sending an analog voltage signal (+/- 10) to a Copley Xenus amplifier (current command) as well as a +5v signal to enable the amplifier. The controller uses position for feedback. When labview errors out, the daq card stays in its current state (and keeps sending the 5v enable signal). For safety reasons, how can I configure my system so that this signal stops being sent out, and the amp is disabled?
Maciek

The program crashed. I shut off the amp. The actuator shaft, which is positioned vertically, dropped to its lowest position due to gravity (it's a linear actuator). The daq card kept pumping out a high force command, due to the large position error created by the disturbance, as well as the 5v enable signal. Upon turning the amp back on, the PD controller saw a large difference between desired and actual position, and the actuator shaft shot up forcefully, creating a very dangerous situation. In the program, I have a case structure which won't enable the amp. unless the difference between desired and actual position is small enough. But the amp stays enabled when labview crashes.
m

Server 2012 R2 disable mapped drives, disables clipboard as well

Hi All,
We have a server 2012 R2 deployment set up, everything is enabled on the gateway for resource redirection, on the server manager RDS deployment it is enabled as well.
Via Group policy computer policy we disable drive redirection and specifically enable clipboard redirection however when logging in as administrator or a standard user they cannot copy and paste from the Session host server to the client.
We then allow drive redirection and copy and pasting from session host to client works again?

when you are saying the clipboard copy and paste - can you confirm if you are referring to copying and pasting text? Or are you meaning copy and paste files?
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
My Blog
LinkedIn:

TI 1394 signed driver only works when driver signing enforcement disabled (Windows 8.1)

I have a Texas Instruments firewire card installed under Windows 8.1. It was working perfectly until recently and now I get a "code 10" in the device manager. It displays as a signed driver when I reinstall it so it should work fine.
However, if I do an advanced reboot with "Disable driver signature enforcement" the driver then seems to work correctly.
Is this a Windows 8.1 bug or a driver bug, and does this mean I have to do an advanced reboot every time I want to use my Motu 828mk3 audio device?
Regards,
CJ.
Can't see the Enabled flag for the... err Enabled flag

Hi,
I cannot find any information about this device in compatibility center, you should contact the device manufacturer to confirm if this driver is designed for Windows 8.1.
Although, we can do some additional analysis about your question.
We can try to go into the %Windir%\Inf folder, when third-party driver installed,
the .inf is renamed to Oemxx.inf (where xx is a sequential number) to make sure that there are no name conflicts with drivers that are included with the product and with other third-party drivers. You can check it one by one, find the right file to get
catalog file, it should be xxx.cat, when you get the catalog file name, you can search this file in windows folder.
To do those actions, is just to confirm if this driver is ok, double-click the .cat file | View Signature | View Certificate | Certification Path and note the highest certificate in the chain. If the result is Microsoft Root Authority,
we need check setupapi.dev.log, there might be some clue about this issue. You can upload it in forum.
Alex Zhao
TechNet Community Support

Installation disabled CD / DVD drives.

Hired MS Assure to fix my email which would not load. Tech recommended upgrading to 2013 which I did. email works fine but I now have NO access to my CD / DVD drives. I have one built in and one external (usb). USB drive operates
fine on my laptop.
I have deleted and restored drivers with no result. Error message in device MGR says: "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change.....etc. Code 52
A portable floppy drive still works as do usb flashdrives.

because maybe installation software change the registry setting, I would suggest you first do clean boot
http://support.microsoft.com/kb/929135
try also reset your BIOS setting
after that try to delete upper lower filter
https://support.microsoft.com/kb/929461/en-us
if doesn't work try to uninstall ODD at device manager and let windows detect your ODD automatically
you can also temporary solved this case by disabling driver signature at advance boot option
http://windows.microsoft.com/en-us/windows/advanced-startup-options-including-safe-mode#1TC=windows-7

DVD/CD optical drive is recognized only occasionally and temporarily

Hi, I recently bought an ASUS Essentio desktop model CG8350 running Windows 7 Home Premium 64-bit. My DVD/CD optical drive is not consistently being recognized. I've made few changes to the computer and have even tried reinstalling Windows (system recovery, factory settings), but no luck. The curious thing is that after booting up I can occasionally temporarily see the D:\ optical drive listed under My Computer or under Device Manager, but after a few seconds or about a minute after restarting or trying to read a disk, this disappears and the optical drive is no longer shown. I would take it back to Best Buy I bought it for repair, but unfortunately that was in the U.S. and I've since moved to Canada. It's frustrating that Best Buy Canada won't honor service warranties for items bought from Best Buy U.S. If there's something I can try in order to avoid shipping it off to ASUS or back to Best Buy U.S. (at my expense, and potential loss of PC for a few weeks), I would much prefer that. These are the things I have tried so far: 1) opening it up and checking/re-plugging the power cable to the optical drive and the data cable between the optical drive and motherboard. All cables seemed fine. The drive ejects and spins a little bit when a disk is inserted, but neither a blank CD/DVD nor a commercial CD are recognised after insertion. 2) looking at the registry to try the "delete UpperFilters" and "delete LowerFilters" trick that I've seen posted several times. Since the computer had Windows 7 from the start (was not upgraded), these entries were not visible under the suggested registry subkey. 3) under boot options, I've selected "Disable Driver Signature Enforcement" and have booted up. The optical drive showed up under My Computer and/or Device Manager for a few seconds or a minute, but then vanished. 4) disabled integrity checks: I've pasted "bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS" into the Run window. After restarting, the optical drive is again occasionally visible, but only for a short period after which it disappears. 5) following a tip on one website, I tried shutting off and unplugging the data cable between optical drive & motherboard, restarting the computer so Windows could "see" there was actually no optical drive connected, then shutting off and connecting the data cable again and restarting. no luck. 6) I've run the Microsoft Support Fixit executable under "Your CD or DVD drive can't read or write media". The first time I ran this, it ran for about 5-10 minutes, but didn't diagnose a problem. The second time I tried to run it (after the Windows 7 re-install), is said my CD/DVD drive was not detected, so didn't run. 7) I've tried built-in Windows diagnostics and ASUS diagnostics, but they didn't help much. 8) I've updated ny BIOS to the most recent version. I've now run out of ideas and can't find any other suggestions on previous troubleshooting searches. The observation of the drive occasionally being seen for a few seconds/minute after start-up before disappearing seems like it might be a good clue, but I'm not sure how to interpret this. I did get it to play an audio CD a couple hours ago, but after trying to use my drive for something else after that, it's right back into the situation of not being consistently recognized, except sometimes immediately after booting up and then only for a short period. Any help or suggestions you have will be very very welcome -- thank you.

Honestly since it was recalled due to the sandy bridge recall anyways, it is going to have to go to asus eventually so I would just have them fix both in one shot. The Canada and U.S. support number is the same and I'm sure they could fix both issues at once to save you time: 1-866-625-9873
Crystal
Superuser
Forum Guidelines | Terms & Conditions | Community Guidelines | What is a Superuser?
*Remember to mark your questions solved and click the star to give kudos to show your thanks!*
While I used to be a Best Buy Employee, I no longer have any affiliation with Best Buy.
My opinions do not in any way shape or form represent Best Buy's Official decisions.

Temporarily disable Digital Signature Checks to Install MS SQL Server 2008 with no Internet Access

I am attempting to install a licensed copy of MS SQL Server 2008 in a Private Enclave that does NOT have Internet access on a Win2008 R2 SP1 server (that is VM - thus I can't reboot and press F8 to select "Disable Driver Signature Enforcement"
). The installation fails with an error of the vc_red.cab file being found either corrupt or a bad digital signature. The file is good, but the signature has an expiration of 2011. I understand that a DOTNET SDK v1.1 program called setreg.exe
will enable disabling the digital signature check, but I am not permitted to use that program.
I might be permitted to use the "Signtool.exe" utility, but it is not clear what command sequences are necessary to disable and then re-enable the Digital Signature checks.
I saw a thread that recommended using the command:
bcdedit.exe /set nointegritychecks ON
However, the comments indicated that this might not have worked.
Are there Registry settings I can use with regedit to make the necessary changes to be able to install the application? I anticipate running into this problem with other software when I do not have Internet connectivity. I already tried
downloading the Microsoft CRL files; updated the lists on the Server; and rebooted. This did not solve my problem.

Hi,
As far as I know, it is not recommended to disable digital signature check.
Since we are not familair with installing MS SQL server, please also refer to SQL forums below to see if experts there have more insights regarding the matter.
https://social.technet.microsoft.com/Forums/sqlserver/en-US/home
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Windows 8 (64) Intel HD 4000 driver wont install on x230t

I have installed all the up-to-date drivers on my x230t running Windows 8 (64), but for some reason this one gives me an error:
"The setup program failed to install one or more drivers. Setup will exit"
Here is the driver for Version 9.17.10.2828
http://support.lenovo.com/en_US/downloads/detail.page?&DocID=DS030728
I downloaded the one directly off the Intel site for their 4000 Graphics chip for windows 8, but its an "older" version.
Any ideas on how to get the newer driver working?
Thanks in advance

You have to disable driver signature verification, because these drivers are not digitally signed.
Go to settings-> change pc settings-> general-> advanced startup to get to the boot menu where you can do this.
After the boot menu appears:
Troubleshoot-> Advanced options-> Startup Settings-> Restart
After the new boot menu appears:
Press 7, disable driver signature enforcement.

Veritas - disabled drives

Similar Messages

Maybe you are looking for