Hello. I'm having this issue after my R2 SP1 upgrade. 

I cannot add drivers to the boot image as the console is hanging.

There is no locks or anything with long waits in the SQL activity monitor.

Its just hanging. 

killing the console leaves the sql lock on the Boot image.



Killing this using process using 

 select LockID from SEDO_LockState where LockStateID <> 0

then 

DELETE from SEDO_LockState where LockID ='result from the first query'

Anyone else having the same problem?

Hi,

It is a known issue that the performance when adding drivers to the Boot Image is challenging, right now there is nothing more to do than wait, it can take up to 30 minuties to add a driver. You don't see anything in SQL as it is the Admin Console that is having problems with adding the drivers.

regards,
Jrgen

I am currently working on OSD and even I face the same issues. When you see the select a driver screen, you need to wait until it collects and displays the drivers. If you hurry and force end the console then you surely see that the boot image will be locked. The same thing happens when you edit the boot image and try to add the drivers.

Be careful while deleting the lock, this is a old technique though but not recommended and should be done with caution.  I hope Microsoft should fix this in the next

I have a 6k and rising driver repository. HP,DELL,LENOVO,Surface. I need to update my boot image drivers. Sort of stuck. I let the console work for over 48 hours over the weekend, and still it didn't show me any drivers in the console. I heard a rumour that powershell will work. :-). Trying that.

Remember, you should not be adding every driver and should only be adding necessary NIC (and sometimes storage) drivers to boot images only if the boot image does not already contain a suitable driver. The only way to know this is to actually boot a system with the boot image -- if it can get to the network and access the local disks, then you don't and should not add any drivers to the boot image as this will bloat your boot image unnecessarily and sometimes it does cause weird conflicts.

I totaly agree with your comments Jason. I can assure you I don't add drivers I don't need to my boot images.  Now with regards to my 6k drivers. The console seems to be struggling with the amount of drivers I have as it has taken over 48 hours !!! and still no drivers listed in my view.

Are you moving drivers into subfolders or leaving them in the default node?

Default node. Can that cause problems?

Not problems necessarily, but it means that every driver must be enumerated for display in the dialog which is already known to take an excessive amount of time. Moving them into subfolders *should* reduce this because only the specific subset of drivers chosen (based on folder) need to be enumerated. The bug will still cause this to take a while, but at least it won't be compounded by having to enumerate them all.