Question: I have one master and one detail table as following

```
Master:-
   BatchID
   BatchStatus
Detail
   DetailID
   BatchID
   DetailRecordStatus (Possible values 1,2,3)

```

I am trying to write a single a query that can update the Batch Status in Master based on `detailRecordStatus` values equal to 2 or 3

Answer: 
I think I've found the cause. 

Most likely the problem is due to ["Fast startup" power options](https://msdn.microsoft.com/en-us/library/windows/hardware/ff547781(v=vs.85).aspx).

[![Fast Startup](https://i.stack.imgur.com/MuuPS.png)](https://i.stack.imgur.com/MuuPS.png)

It'a a Windows technique to reduce the boot time; Fast Startup combines elements of a [cold shutdown and the hibernate feature](https://msdn.microsoft.com/en-us/library/windows/hardware/jj835779(v=vs.85).aspx).

Here you can find another [article](https://www.howtogeek.com/243901/the-pros-and-cons-of-windows-10s-fast-startup-mode/) about pros and cons

I have disabled it and the problem seems to be resolved.
These are my observations and how I solved the problem (for the benefit of others who may have the same problem)

* I was using amazon ec2 instance running Sql server.
* I had an EBS Block device attached to the ec2 instance, that mapped to the D: drive.
* My data and logs were in the D: drive.
* When I stop the ec2 instance and bring it up later, I always experienced the error of "device not ready" and the databases would not come up.
* I tried setting the MSSQLSERVER service with "Delayed startup".
* However, from the sql server logs I found that the delay was not honored and MSSQLSERVER started up right along with the boot.
* From the eventviewer I observed the time at which the D: drive becomes healthy.
* From the sql server logs, I noted the time at which SQL Server is starting up my user database.
* I observed that, D: drive is only available after 6 seconds later; and obviously the "Device not ready" error shows up.
* I also noted that that the "Delayed start" was not honored because there was another service named "SQL SERVER LaunchPad" which startups up "MSSQLSERVER".
* I don't need the Analytics capability of the "Launchpad". So I disabled that service.
* **Now "MSSQLSERVER" starts up with a delay and can find the D: drive files.**