Announcement

Collapse
No announcement yet.

Acces denied error on Windows 10 and DT Ultra 4.1

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Acces denied error on Windows 10 and DT Ultra 4.1

    Hello,

    I haven't used daemon tools until recently and I am unable to mount images anymore. Each time and for each image format I tried I get an access denied error popup.

    I tried cue+bin, iso, zip. I tried on several location on my drives, C: and D: which are physically different (not partitions).

    I can obviously read the files. I also tried running daemon tools as administrator with no result.

    What can go wrong ?

    I am using Windows 10 64 bits and DT Ultra 4.1

    Thanks

  • #2
    Hello,

    Need more details. How do you mount, DT, SCSI, This problem has all images you try or specific?
    Don't worry! Be Happy!

    Comment


    • #3
      Hello,

      I have this issue with all images I try.
      To reproduce, I add an iso image to the image folder inside DT, every thing goes fine. I even have the icon changed to the one defined in the autorun.inf file. But when I double-click to mount I have then the popup error.
      I also tried with a saturn or psx cue+bin image with the same result. No error is shown until I try to mount it.

      I am using windows 10 pro edition x64 french with all the updates


      I have no error in the event logs, just a success message in the system logs :
      La gestion des pilotes a terminé le processus d’installation du pilote cdrom.inf_amd64_9693c41d66f6eee1\cdrom.inf pour l’ID d’instance de périphérique DTULTRASCSIBUS\CDROM&VEN_DISCSOFT&PROD_VIRTUAL&REV _1.0\1&2AFD7D61&3&0000 avec le statut suivant : 0x0.
      ==> Driver manager finished to install installation process from driver cdrom.inf_xxxx for device id DRULTRASCSIBUS\xxxx with status 0

      I do have though an informational event in the application log :

      Récipient d’erreurs , type 0
      Nom d’événement : PnPDeviceProblemCode
      Réponse : Non disponible
      ID de CAB : 0

      Signature du problème :
      P1 : x64
      P2 : SCSI\CdRomDiscSoftVirtual_________1.0_
      P3 : {4d36e965-e325-11ce-bfc1-08002be10318}
      P4 : 00000013
      P5 : cdrom.sys
      P6 : 10.0.10586.0
      P7 : 10-30-2015
      P8 :
      P9 :
      P10 :

      Fichiers joints :

      Ces fichiers sont peut-être disponibles ici :
      C:\ProgramData\Microsoft\Windows\WER\ReportQueue\N onCritical_x64_cbf2cd222ca1ca1d8e6b5d585c3bc34c9c4 826d_00000000_1d0d9383

      Symbole d’analyse :
      Nouvelle recherche de la solution : 0
      ID de rapport : aec1c9a9-db2e-11e5-9c60-74d02b931efb
      Statut du rapport : 96
      Récipient avec hachage :

      The report file pointed by the previous message only has this content :

      Version=1
      EventType=PnPDeviceProblemCode
      EventTime=131008165261592383
      Consent=1
      UploadTime=131008165270231624
      ReportIdentifier=aec1c9a9-db2e-11e5-9c60-74d02b931efb
      Response.type=4
      Sig[0].Name=Architecture
      Sig[0].Value=x64
      Sig[1].Name=ID du matériel
      Sig[1].Value=SCSI\CdRomDiscSoftVirtual_________1.0_
      Sig[2].Name=GUID de classe d’installation
      Sig[2].Value={4d36e965-e325-11ce-bfc1-08002be10318}
      Sig[3].Name=Code de problème PnP
      Sig[3].Value=00000013
      Sig[4].Name=Nom du pilote
      Sig[4].Value=cdrom.sys
      Sig[5].Name=Version du pilote
      Sig[5].Value=10.0.10586.0
      Sig[6].Name=Date du pilote
      Sig[6].Value=10-30-2015
      DynamicSig[1].Name=Version du système
      DynamicSig[1].Value=10.0.10586.2.0.0.256.48
      DynamicSig[2].Name=Identificateur de paramètres régionaux
      DynamicSig[2].Value=1036
      FriendlyEventName=Impossible de charger le pilote.
      ConsentKey=PnPDeviceProblemCode
      AppName=DiscSoft Virtual SCSI CdRom Device
      AppPath=C:\Windows\System32\drvinst.exe
      ReportDescription=Windows installé correctement le pilote du périphérique, mais le pilote a rencontré un problème d'exécution. Le code du problème est 19.
      ApplicationIdentity=000000000000000000000000000000 00

      ==> FriendlyEventName=Unable to load driver
      ==> ReportDescription=Windows successfully installed device drive but the driver encountered an issue. Issue id is 19.



      Does DT generate a verbose log file ?


      One thing I have noticed is I no longer have the DT drive listed in "My Computer" and I don't know what to do to create it again. Any clues ?

      Comment


      • #4
        Problem solved.

        The issue was not from Daemon Tools but from the anydvd uninstaller which leave a mess in the registry.

        Steps to fix are here.

        Comment

        Working...
        X