Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

OSR Seminars

Go Back   OSR Online Lists > ntfsd
Welcome, Guest
You must login to post to this list
  Message 1 of 2  
05 Sep 17 17:31
Rehan Rizvi
Join Date: 06 Jan 2015
Posts To This List: 1
Why adding a drive letter makes a difference?

Hi, I am mounting a VHD as C:\Windows\SoftwareDistribution folder. I then run Windows Updates. Now this works on all previous versions of Windows that supported a VHD, but on Windows 10 1703 it fails with error code 0x8024005d (WU_E_UNRECOGNIZED_VOLUME_ID). Now the funny thing is, if I assign a drive letter in addition to the first mount point it works. I was wondering why adding a drive letter makes a difference? Any input regarding the question will be appreciated. Thank R
  Message 2 of 2  
06 Sep 17 03:44
rod widdowson
Join Date: 11 Sep 2006
Posts To This List: 857
Why adding a drive letter makes a difference?

In my experience Windows Update is a strange beast and its ways are mysterious, it isn't necessarily written by people who understand the kernel side of things and an assumption that all volumes must have drive letters seems like the sort of thing that can happen. It can take umbrage at the least things and the best to do is placate it. R
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntfsd list to be able to post.

All times are GMT -5. The time now is 21:44.

Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license