Computer crashed and D:/ disappeared along with reboot issue

[wainuitech]

I install every patch that comes along so assumed it was up-to-date

Bryan is 100% correct, you have a old Build, that's actually build 1803, which is close to a year out of date.

If you open Winver Via the search it should show, prob 1803 ( highlighted in the picture).I've manually upgraded to the latest:



What more than likely has happened in when 1809 came out ( the current public build) it was pulled /stopped because of a bug, when MS re -released it again, a HUGE number of computers didn't upgrade.

Having the second drive as D is not a good idea.

Cant explain the technical details right now ( SWMBO) is calling.

BUT as a quick experiment, go into drive manager, re assign a different Drive letter to the current D, F,H I -- what ever anything but D.

[DeSade]

Bryan is 100% correct, you have a old Build, that's actually build 1803, which is close to a year out of date.

If you open Winver Via the search it should show, prob 1803 ( highlighted in the picture).I've manually upgraded to the latest:



What more than likely has happened in when 1809 came out ( the current public build) it was pulled /stopped because of a bug, when MS re -released it again, a HUGE number of computers didn't upgrade.

Having the second drive as D is not a good idea.

Cant explain the technical details right now ( SWMBO) is calling.

BUT as a quick experiment, go into drive manager, re assign a different Drive letter to the current D, F,H I -- what ever anything but D.

How can I upgrade the OS then?

What will happen to shortcuts and everything else that points to D?

[wainuitech]

Assuming its at 1803, check With Winver ( from Search, then open and check)



If its 1803, you can manually upgrade to the current Public Build 1809, via the media creaton tool, several options - have a read. ( wont post how to get 1903 YET as its still not public released and they still have a couple of minor fixes before they do.

https://www.microsoft.com/en-us/soft...load/windows10

If you download it you can make an ISO or use a flash drive ( thats from Downlaod Tool Now)

Leave the drive letter as is for the mean time.

Remember anyone here cant see how you have things setup ( what goes where etc) this is why often its 20 Questions. Where as seing in front of the screen its easier.

NOTE: upgrading can take 5-6+ hours or more depending on what has to be done (within Windows automatically)

[DeSade]

Yeah I know no one can see what I have and I expect to be questioned.
I would put the answers in advance I just don't know what I will be asked.

Does any of this relate to the issue I have with rebooting?

The D drive situation has sorted itself out now that the machine managed to reboot.

[piroska]

Forget the OS version.
It shouldn't do that whatever latest or not anything.

Test it with a Linux boot...you don't need to install..........

I'd say thats a hardware issue. What hardware? Well, that's going to take some troubleshooting, what does Event Viewer say, if anything?

[DeSade]

Forget the OS version.
It shouldn't do that whatever latest or not anything.

Test it with a Linux boot...you don't need to install..........

I'd say thats a hardware issue. What hardware? Well, that's going to take some troubleshooting, what does Event Viewer say, if anything?

Nothing in Event Viewer that I can see

Harware

ASUS X99-E WS/USB3.1 Intel X99 DDR4 LGA2011 WorkStation Motherboard
Intel Haswell-E Core i7 5960X 8 Core 16 Threads 3.0Ghz 20M Cache LGA2011
Corsair Dominator 16GB (2x8GB) DDR4-2666 x2
Samsung 950 PRO 256GB M.2 NVMe SSD
Seagate SSHD ST4000DX001 4TB 64MB Solid State Hybrid Drive SATA3 x3
Gigabyte Aorus GeForce GTX1080TI 12GB Waterforce Xtreme
Corsair AX Series AX1500i Digital 1500W Modular Power Supply 80Plus Titanium
Thermaltake View71 T Case

[CliveM]

All of the My folders are there, as well as all of my gaming data, the actual game installs are elsewhere but without the data they are blank, no character saves, no game saves, no mod files all on D. The worse part is my backup is also physically on D as a partition of it.

I am sure you already know this! A backup should not be placed on the same disk as the data you are backing up it should be on a drive which is physicaly separate from from your PC. That way you can easily restore things if it all turns to custard.

[DeSade]

I am sure you already know this! A backup should not be placed on the same disk as the data you are backing up it should be on a drive which is physicaly separate from from your PC. That way you can easily restore things if it all turns to custard.

Yes but that is not practical.
I am not backing up to the cloud and this computer is not connected with anything else that is large enough to hold its backup.

[1101]

Assuming you dont have a CD\DVD drive ....... ( causing conflicts with drive lettering, D: )

Could be that 2nd hard drive is starting to fail. That may be why it works or doesnt on a whim :-)

Get a good backup of that 2nd drive .
I wouldnt worry about ~only~ having v1803. There are hundreds of thousands (millions?) of PC's working happily with 1803
If 1809 was important to have, MS would have forced that upgrade onto all Win10 PC's .
I would wait untill your PC is stable before upgrading to 1809 , or just wait untill the next big Win10 build update (just an opinion)

[DeSade]

Assuming you dont have a CD\DVD drive ....... ( causing conflicts with drive lettering, D: )

Could be that 2nd hard drive is starting to fail. That may be why it works or doesnt on a whim :-)

Get a good backup of that 2nd drive .
I wouldnt worry about ~only~ having v1803. There are hundreds of thousands (millions?) of PC's working happily with 1803
If 1809 was important to have, MS would have forced that upgrade onto all Win10 PC's .
I would wait untill your PC is stable before upgrading to 1809 , or just wait untill the next big Win10 build update (just an opinion)

I do not have any optical drives in this machine.

Its never showed any indication of failure and this is the first and only time its ever disappeared like that.
This seems to be a windows issue rather than a drive issue and it is all working fine now.