Jump to content

Recommended Posts

hi,

a while ago i ran a MB scan with root kit detection on and it quarantined microsoft files.  i had mb put them back. when i booted win 10 had a problem, but seemed to resolve itself and i ignored it,  mb was trial 3.0.6.  apparently it was not current, but i always tell mb to update itself when i used it.  since then my audio stopped working and after looking at the c:\windows\inf\setupapi.dev.log where the audio update install is i can see that my drmk.sys file is missing so i cannot complete a driver install and correct my audio problem.  i looked, there is no drmk.sys file on my pc...  i had subsequently uninstalled mb then installed the current ver so i have no mb log.  i am running win 10 15063.608.  can you help?  i cannot find any source for drmk.sys.

 

thanks

 

Link to post
Share on other sites

Since you're on Windows 10, you can also run the following command from an Administrator Command prompt, which should restore the file for you.

dism /online /cleanup-image /restorehealth

This command could take awhile to finish

If that doesn't work, try doing a search in the following folder for drmk.sys: C:\Windows\WinSxS. This should have a backup of most of your system files. There may be multiple files, but the easiest solution is to look for the latest one and try there, if that doesn't work, then go back.

 

Link to post
Share on other sites

hi,

i ran dism and got this:

C:\WINDOWS\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[===========================95.7%=======================   ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature.

 

 

so i ran dism pointing to a win 10 iso i created 2 weeks ago

C:\Windows\Logs\DISM>DISM /Online /Cleanup-Image /RestoreHealth /source:e:\sources

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[===========================95.7%=======================   ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature.

 

here is e:

C:\Windows\Logs\DISM>dir e:
 Volume in drive E is CCSA_X64FRE_EN-US_DV5

 Volume Serial Number is D1EE-B187

 Directory of E:\

02/10/2017  02:22 PM               128 autorun.inf
03/18/2017  10:49 PM    <DIR>          boot
03/18/2017  01:14 AM           395,220 bootmgr
03/18/2017  02:28 AM         1,203,616 bootmgr.efi
03/18/2017  10:49 PM    <DIR>          efi
03/18/2017  01:40 AM            80,704 setup.exe
03/18/2017  11:18 PM    <DIR>          sources
03/18/2017  10:50 PM    <DIR>          support
               4 File(s)      1,679,668 bytes
               4 Dir(s)               0 bytes free

 

i found a drmk.sys file in C:\Windows\WinSxS, but it was only 12 bytes, not correct.  no other finds.

 

help please.

 

Link to post
Share on other sites

Did you try putting the 12 byte file in place? That's the same size as mine. You can also look in \Windows\System32\DriverStore\FileRepository and search for the file in those subfolders.

If none of that works, please upload your the following two logs (you may need to zip them):

  • \Windows\logs\cbs\cbs.log
  • \Windows\logs\dism\dism.log
Link to post
Share on other sites

ok.  so this was the error in the setupapi.dev.log that pointed me to dmrk

!!!  flq:                Source Media: SPFQOPERATION_ABORT (C:\WINDOWS\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_d971d3ff1aaf7bdb\drmk.sys).
!!!  flq:                Error 2: The system cannot find the file specified.

it wasn't in that dir.

so where do you want me to put the 12 byte file, in there, or anywhere else?  thanks.

Link to post
Share on other sites

ok.  i can do that, but it won't fix the audio installer problem because that looks in DriverStore\FileRepository\wdmaudio.inf_amd64_d971d3ff1aaf7bdb for drmk.

so after i put it in drivers what should i do then?  or will putting it in there correct the audio problem if i reboot?

Link to post
Share on other sites

Yes, thanks.  But I do see there is a big drmk.sys and a small one.  And the big one is an ms trusted audio driver.  Why can't dism bring that one back from the Net or a win 10 iso?

Msoft suggests rolling back with restore point if I can associate a date with the problem start.  Unfortunately all my restore points before my last critical update are gone.  Very ironic.

 

Link to post
Share on other sites

dism won't bring that one back for a few reasons. The most common is that it's missing from the required location, the second most common is that it's the wrong one. Do you have the same files as Firefox listed above? Can you do the same search (GO to C:\Windows and then search for drmk.sys) and post a screenshot? We have a few ways we can quickly test all the relevant files.

Link to post
Share on other sites

Ok, looking over all the data, we probably do need that larger file. If you have another Windows 10 computer that is running properly, you can try copying the entire C:\WINDOWS\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_d971d3ff1aaf7bdb\ from there, and putting it in the same place on your broken computer, then running that dism command again. Do you have another computer you can copy it from? (Note, you need to make sure the folder name is exactly the same, especially the numbers/letters at the end)

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.