Enable Camera in Device Manager

[ClaudiuZ]

hi guys!

i'm new on autoit and i like this script, and i want to used for a situation in my company where we have 500 notebooks with camera disabled, but i dont know where to put my simple script.

here is my script:

MsgBox(0,"Enable WebCamera!", "Now I will enable your Computer Camera for your next Skype meetings!", 2)
run("\\...\computer management.bat", "", @SW_MAXIMIZE)
WinWaitActive("Computer Management")
Sleep (500)
Send("{device}")
WinWaitActive("Computer Management")
Sleep(500)
Send("{TAB}")
WinWaitActive("Computer Management")
Sleep(500)
Send("{DOWN 9}")
WinWaitActive("Computer Management")
Sleep(500)
Send("{APPSKEY}")
WinWaitActive("Computer Management")
Sleep(500)
Send("{DOWN 2}{ENTER}")
WinClose ("Computer Management")

 

can you help me?

thanks

[JLogan3o13]

@ClaudiuZ I have moved your post to the main Help and Support thread, as it had nothing to do with the old thread you posted in. 

[ClaudiuZ]

@JLogan3o13 yes but it was linked to the upper post!

 

[Bert]

ClaudiuZ, 

   There are multiple issues with your script. 

1. Don't use send unless you have no choice. Use ControlSend instead. The reason is if the script loses focus with the window it intends to send a click or text to, your script breaks. 
2. If you have to use Send - I can see you are trying to tab around the window to get to the control you need. IF BY ANY CHANCE there is an extra device installed it be a software device or hardware in your case - your script WILL break. with 500 machines - the odds of that are very high even though you may have the machines locked down. 
3. You are having to touch 500 machines and you can bet your hat a user will interrupt your script. Many users HATE using the camera and if they know you are trying to enable the camera, they WILL try to block it. May I suggest you do it with command line. Look at this: https://superuser.com/questions/429016/enable-disable-windows-7-device-via-command-line 

If I was you - do it with command line. That way there is little chance of failure. 

[ClaudiuZ]

@Bert, thank you for info.

the user not have possibility to eject a installation because is do it from a deployment software.

i will try with what do you recommend it. but if you know where to put my basic script in this script i will be grateful :

thanks to @storme and @lbw87 for the script

#RequireAdmin
;==================================================================================
; function is used to determine if there are any issues in the device manager
;==================================================================================

    Dim $bProblemsExist, $bDisabledExist, $Code = "", $codemsg = ""
    $bProblemsExist = false
    $bDisabledExist = false
$strComputer = "."

DeviceProblems()

Func DeviceProblems()
$DEVobjWMIService = ObjGet("winmgmts:\\" & $strComputer & "\root\cimv2")
$DEVcolItems = $DEVobjWMIService.ExecQuery("Select * from Win32_PnPEntity " & "WHERE ConfigManagerErrorCode <> 0")
For $DEVobjItem in $DEVcolItems
    $Code = $DEVobjItem.name & ": "
  if $DEVobjItem.ConfigManagerErrorcode = 1 Then
   $bProblemsExist = True
   $Code &= "System Failure - No Config"
   $codemsg = "Verify you have the latest driver installed for your device. You may also be able to resolve this issue by removing the device in Device Manager and going through the Add New Hardware Wizard in Control Panel"
  Elseif $DEVobjItem.ConfigManagerErrorcode = 2 Then
   $bProblemsExist = True
   $Code &= "Device could not load driver"
   $codemsg = "Verify you have the latest driver installed for your device. You may also be able to resolve this issue by removing the device in Device Manager and going through the Add New Hardware Wizard in Control Panel."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 3 Then
   $bProblemsExist = True
   $Code &= "System Failure - Run Out of Memory"
   $codemsg = "Verify you have the latest driver installed for your device. You may also be able to resolve this issue by removing the device in Device Manager and going through the Add New Hardware Wizard in Control Panel."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 4 Then
   $bProblemsExist = True
   $Code &= "Device Failure - Devloader/Static VxD/Configured is of Wrong Type."
   $codemsg = "This code indicates that the .inf file for this device may be incorrect or the registry may be damaged. This error code is displayed if the .inf file specifies a field that should be text, but is binary instead. In addition to following the recommended suggestions, use Device Manager to remove the device, then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, please contact the hardware's manufacturer for an updated .inf file. "
  Elseif $DEVobjItem.ConfigManagerErrorcode = 5 Then
   $bProblemsExist = True
   $Code &= "Device Failure - Lacked an Arbitrator."
   $codemsg = "Verify you have the latest driver installed for your device. You may also be able to resolve this issue by removing the device in Device Manager and going through the Add New Hardware Wizard in Control Panel. "
  Elseif $DEVobjItem.ConfigManagerErrorcode = 6 Then
   $bProblemsExist = True
   $Code &= "Boot config Conflicted."
   $codemsg = "One or more of your devices within your computer are conflicting, such as an IRQ conflict. Ensure that the IRQs DMA, and I/O addresses are all correct."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 7 Then
   $bProblemsExist = True
   $Code &= "Filtering Failed - Possible problem in Device Driver Code."
   $codemsg = "If the device works correctly, you do need not to perform any steps to correct the code. If the device does not work correctly, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code and the device does not function properly, check with the hardware manufacturer for an updated driver. "
  Elseif $DEVobjItem.ConfigManagerErrorcode = 8 Then
   $bProblemsExist = True
   $Code &= "System failure - Devloader Not Found"
   $codemsg = "If you are receiving an error about Devloader, there is no known resolution. If you are receiving any other error, reinstall the driver or update the driver. If you are getting an error with a System Devloader, Windows should be reinstalled because the Devloader is built into the Vmm32.vxd."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 9 Then
   $bProblemsExist = True
   $Code &= "Invalid Data in Registry."
   $codemsg = "This code means that the information in the registry for this device is invalid. It may be possible to resolve this error by using Device Manager to remove the device, then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, contact the hardware's manufacturer for the proper registry settings or updated drivers. "
  Elseif $DEVobjItem.ConfigManagerErrorcode = 10 Then
   $bProblemsExist = True
   $Code &= "Device Failed to start."
   $codemsg = "Verify you have the latest driver installed for your device. You may also be able to resolve this issue by removing the device in Device Manager and going through the Add New Hardware Wizard in Control Panel."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 11 Then
   $bProblemsExist = True
   $Code &= "Device Failure."
   $codemsg = "To resolve this error, run the Automatic Skip Driver utility from the System Information tool. If the problem persists, contact the hardware manufacturer for updated drivers. "
  Elseif $DEVobjItem.ConfigManagerErrorcode = 12 Then
   $bProblemsExist = True
   $Code &= "Was normal conflicting - One of the resource arbitrators returned a failure. "
   $codemsg = "One or more of your devices within your computer are conflicting, such as an IRQ conflict. Ensure that the IRQs DMA, and I/O addresses are all correct."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 13 Then
   $bProblemsExist = True
   $Code &= "System Failure - Possible problem in Device Driver or Windows 95 Code. "
   $codemsg = "This code indicates that the device driver did not find the hardware. To resolve this error code, first ensure the device is properly installed. As an alternative, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. "
  Elseif $DEVobjItem.ConfigManagerErrorcode = 14 Then
   $bProblemsExist = True
   $Code &= "Need to restart your computer for this device to be re setup or to be finished installed."
   $codemsg = "Restart the computer"
  Elseif $DEVobjItem.ConfigManagerErrorcode = 15 Then
   $bProblemsExist = True
   $Code &= "This device is causing a resource conflict."
   $codemsg = "One or more of your devices within your computer are conflicting, such as an IRQ conflict. Ensure that the IRQs DMA, and I/O addresses are all correct."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 16 Then
   $bProblemsExist = True
   $Code &= "Was not fully detected, not all detected."
   $codemsg = "Double-click on the device, click the Resources tab and manually enter the settings. "
  Elseif $DEVobjItem.ConfigManagerErrorcode = 17 Then
   $bProblemsExist = True
   $Code &= "Device failure - Resource number was not found."
   $codemsg = "This code means that the hardware is a multiple-function device and the .inf file for the device is providing invalid information on how to split the device's resources to the child devices. To resolve this error code, use Device Manager to remove the device, then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, contact the hardware's manufacturer about an updated .inf file. "
  Elseif $DEVobjItem.ConfigManagerErrorcode = 18 Then
   $bProblemsExist = True
   $Code &= "Reinstall."
   $codemsg = "Verify you have the latest driver installed for your device. You may also be able to resolve this issue by removing the device in Device Manager and going through the Add New Hardware Wizard in Control Panel."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 19 Then
   $bProblemsExist = True
   $Code &= "System Failure - Registry returned unknown result"
   $codemsg = "Problem in the registry. If you have Windows 95 and you have not made a backup of the registry you will need to reinstall Windows.If you have Windows 98: To resolve this issue, follow the recommended solution, which will run Scanreg.exe. If this does not resolve the issue, type scanreg /restore from C:\Windows\COMMAND. "
  Elseif $DEVobjItem.ConfigManagerErrorcode = 20 Then
   $bProblemsExist = True
   $Code &= "System Failure - VxDLdr Returned Unknown Result."
   $codemsg = "This code means VxD Loader (Vxdldr) returned an unknown result. For example, there could a version mismatch between the device driver and the operating system driver. Update the driver. If that does not work, try removing the device from Device Manager and then running the Add New Hardware Wizard in Control Panel. "
  Elseif $DEVobjItem.ConfigManagerErrorcode = 21 Then
   $bProblemsExist = True
   $Code &= "Will Be Removed."
   $codemsg = "Restart the computer."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 22 Then
   $bDisabledExist = True
   $Code &= "This device is disabled."
   $codemsg = "Double-click on the device and Enable. If this does not work, update the driver. If this also does not work, remove the device and reinstall through Add New Hardware Wizard in Control Panel."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 23 Then
   $bProblemsExist = True
   $Code &= "Device Failure - Devloader was not ready."
   $codemsg = "Verify you have the latest driver installed for your device. You may also be able to resolve this issue by removing the device in Device Manager and going through the Add New Hardware Wizard in Control Panel."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 24 Then
   $bProblemsExist = True
   $Code &= "Device not Found, This device is either missing or not working properly."
   $codemsg = "Verify you have the latest driver installed for your device. You may also be able to resolve this issue by removing the device in Device Manager and going through the Add New Hardware Wizard in Control Panel."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 25 Then
   $bProblemsExist = True
   $Code &= "Was Moved - Possible problem in device driver code."
   $codemsg = "Attempt first to restart the computer at least two times, if you continue to get this error, Reinstall Windows."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 26 Then
   $bProblemsExist = True
   $Code &= "Device Failure."
   $codemsg = "First restart the computer. If this does not resolve the issue, check for updated drivers. In some cases, this issue may also be resolved by removing the device in Device Manager and going through the Add New Hardware Wizard in Control Panel."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 27 Then
   $bProblemsExist = True
   $Code &= "Device failure - No Valid Log configuration"
   $codemsg = "This code means that the portion of the registry describing possible resources for a device does not contain valid entries. For example, the device is marked as configurable, but the configuration information in the .inf file is set to hardwired. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If the device still does not work, consult the hardware manufacturer for updated drivers or further assistance. "
  Elseif $DEVobjItem.ConfigManagerErrorcode = 28 Then
   $bProblemsExist = True
   $Code &= "Failed Installation - This device was not installed completely."
   $codemsg = "Verify you have the latest driver installed for your device. You may also be able to resolve this issue by removing the device in Device Manager and going through the Add New Hardware Wizard in Control Panel."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 29 Then
   $bProblemsExist = True
   $Code &= "Hardware Disabled - This device does not work and cannot be made to work."
   $codemsg = "Ensure that the device is not disabled through BIOS. Many times Windows cannot override settings in the BIOS. If the device is enabled there is no other known resolution."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 30 Then
   $bProblemsExist = True
   $Code &= "Cant Share IRQ."
   $codemsg = "A PCI/EISA SCSI controller is sharing an IRQ that is also in use by a real-mode device driver set not to be overwritten. Remove the real mode driver that is using the same IRQ as the device from the config.sys or autoexec.bat."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 31 Then
   $bProblemsExist = True
   $Code &= "<device> is not working properly."
   $codemsg = "The properties button displays the properties for the other device. More than likely the other device will also have one of these Device Manager error codes. Follow all the recommended solutions. If the devices still do not work remove the devices from Device Manager and use the Add New Hardware wizard in Control Panel to redetect them. Finally, verify that your devices have the latest drivers. "
  Elseif $DEVobjItem.ConfigManagerErrorcode = 32 Then
   $bProblemsExist = True
   $Code &= "Cannot install the device because cannot access the Networked drive."
   $codemsg = "First, restart the computer. If this does not resolve your issue, verify that the device you are attempting to copy from is properly working. If the device is working, verify you have the latest drivers from the manufacturer."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 33 Then
   $bProblemsExist = True
   $Code &= "Device is not responding."
   $codemsg = "This error is usually only shown when hardware device has failed. Suggest replacing the hardware device."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 34 Then
   $bProblemsExist = True
   $Code &= "The device requires manual configuration."
   $codemsg = "Set the jumpers for the device and configure the device manually through Device Manager. If this device has worked in the past and has stopped working uninstall any recently installed programs."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 35 Then
   $bProblemsExist = True
   $Code &= "BIOS does not contain necessary resource assignments."
   $codemsg = "Obtain the latest BIOS update."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 36 Then
   $bProblemsExist = True
   $Code &= "IRQ translation failed."
   $codemsg = "Adjust the IRQ reservation settings in CMOS (BIOS) setup."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 37 Then
   $bProblemsExist = True
   $Code &= "The DriverEntry routine failed when attempted by this driver."
   $codemsg = "Download and install the latest driver for the device with the error. If you're running the 64-bit version of Windows, make sure you're installing a 64-bit driver and not a 32-bit driver."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 38 Then
   $bProblemsExist = True
   $Code &= "The driver cannot load because a previous instance is still loaded."
   $codemsg = "Restart the computer. If after restarting the computer the issue persists, download the latest drivers from the manufacturer, uninstall the current driver, and then install the latest drivers."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 40 Then
   $bProblemsExist = True
   $Code &= "Information in the registry entry for this driver is invalid."
   $codemsg = "Download the latest drivers from the manufacturer, uninstall the current driver, and then install the latest drivers."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 41 Then
   $bProblemsExist = True
   $Code &= "A driver was loaded but Windows cannot find the device. "
   $codemsg = "Download the latest drivers from the manufacturer, uninstall the current driver, and then install the latest drivers."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 42 Then
   $bProblemsExist = True
   $Code &= "Bus driver has created two devices with the same names."
   $codemsg = "Restart the computer."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 43 Then
   $bProblemsExist = True
   $Code &= "A device driver notified the operating system that the device failed."
   $codemsg = "This error is usually only shown when hardware device has failed. Suggest replacing the hardware device."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 44 Then
   $bProblemsExist = True
   $Code &= "The device driver was stopped by other software on the computer."
   $codemsg = "Restart the computer."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 45 Then
   $bProblemsExist = True
   $Code &= "The device is not present or was previously attached to the computer."
   $codemsg = "Re-attach the disconnected device."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 46 Then
   $bProblemsExist = True
   $Code &= "The device is not available because the computer is shutting down."
   $codemsg = "The computer is in the process of shutting down. When computer restarts the device should function as normal."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 47 Then
   $bProblemsExist = True
   $Code &= "The device is ready for removal."
   $codemsg = "Unplug the hardware device and plug it back in or restart the computer."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 48 Then
   $bProblemsExist = True
   $Code &= "Driver incompatibility."
   $codemsg = "Download the latest drivers from the manufacturer, uninstall the current driver, and then install the latest drivers."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 49 Then
   $bProblemsExist = True
   $Code &= "The system hive has exceeded its maximum size and new devices cannot work until the size is reduced. "
   $codemsg = "Uninstall any un-used hardware devices."
  Elseif $DEVobjItem.ConfigManagerErrorcode = 52 Then
   $bProblemsExist = True
   $Code &= "The driver may be unsigned or corrupted. "
   $codemsg = "Download the latest drivers from the manufacturer, uninstall the current driver, and then install the latest drivers."
  Else
   $codemsg = "Device Manager is Clean"
  EndIf
ConsoleWrite("Device Manager Error Found!! " & @CRLF & $Code & " " & $codemsg & @CRLF & @CRLF)
;msgbox(4096,$Code,$codemsg)

Next

If $bDisabledExist = False And $bProblemsExist = False Then
$Code = "No Problems Found!!"
$codemsg = "Device Manager is Clean."
ConsoleWrite($Code & " " & $codemsg & @CRLF)
EndIf
EndFunc

Edited November 14, 2018 by ClaudiuZ
wrong code

[ClaudiuZ]

@Bert the situation is that i need to check if camera is disabled, and if is it then i need to enabled!

i dont know ho to do it with devcon

[Nine]

5 hours ago, ClaudiuZ said:

@Bert the situation is that i need to check if camera is disabled, and if is it then i need to enabled!

i dont know ho to do it with devcon

Who will be enabling it you (at distance) or the notebook user ?

[Melba23]

ClaudiuZ,

Nine makes a very valid point - and until I have a satisfactory answer this thread goes nowhere.

M23

P.S. And just to be absolutely clear - this is the Mod team determining the legality of the thread, so everyone else please keep out.

[ClaudiuZ]

@Nine i need to put it on deployment server for automatically install on all notebooks!

 

[Melba23]

ClaudiuZ,

Not a good enough response. Please answer the question as it was asked:

"Who will be enabling [the camera] you (at distance) or the notebook user ?"

M23

[ClaudiuZ]

@Melba23 i will enable remotely on all notebooks!

  

[Melba23]

ClaudiuZ,

In that case we are not prepared to help you as the possibility of such code being used for nefarious purposes is far too high - thread locked.

M23

 

[Melba23]

ClaudiuZ,

You PMed me asking for help to enable the user to enable the camera. As long as the thread remains focused on actions to be taken by the user and not any form of remote activation of the camera I am prepared to reopen the thread.

One ploy that springs to mind would be to display a dialog to the user asking them to activate the camera - and possibly not allowing Skype to run until this is not done.

M23

 

[Bert]

You know what would be the simplest way to do it - just write a PowerPoint deck with animation showing the user how to do it themselves. 

A second way would be a video showing the users.

A third way is a word doc with screenshots

[Nine]

I would suggest a small script based on devcon, that would enable the camera.  That has to be done by user, noway can someone remotely could activate it. Can you give me the name of the camera device you are looking at ?  If you need help finding it let me know...

Edit : maybe some user would like to disable the camera. Then the script should allow both enabling and disabling !

Edited November 16, 2018 by Nine