OK, I get it. Technology can't be "forward" compatible, but something happened to me over the weekend that really "churns my butter". This week Microsoft has been creating headlines because their new Anniversary update seems to be breaking webcams. Well, it appears to me that maybe more than webcams are being affected, let me share with you what I discovered.
I need to first setup the story.
I'm a "living on the edge" kind of guy (I listened to too much Aerosmith) which sometimes works against me, as I like to see what's coming at all of us by running the latest and greatest. So it shouldn't surprise you all that on my Windows 10 Enterprise system, I'm apart of the Microsoft Insiders club, which means I get to play around with upcoming features before they are released to the general public.
So I just finished up recording my Ethical Hacking series of videos with Pluralsight and figured it was time to re-image my system so I could have that "fresh and clean feeling" after all the dirty hacking I had done. Now my systems isn't your normal everyday desktop machine (NERD ALERT! I'm about to brag about my AWESOME setup to make you all feel inferior and allow me to push out my chest a bit ;-) ). I'm running a i7 with 32GB RAM. I'm using 2 SSD drives (one for my OS the other for virtual machines). I then have 5 HD's for storage (2-2TB + 3-3TB) with these 5 drives, I use the coolest feature ever on Windows 10 called Storage Spaces (I know, it was release with Windows 8.1, but that's not the point!), to create a 12TB storage pool. This is were I store all my data, static VM's, Batman comics, etc. In the past this hasn't been an issue at all...ever. Until now.
So here's what I found out. I started my re-imaging process by inserting my famous "BatDrive"
into my system and booted off of it. I went through the process of installing Windows 10 Enterprise with no issue, until I went and looked at my storage spaces (had to get some program files to install) and BAM! Major-Issue. The physical drives show up under the Storage Spaces console, but all the drives were listed as "Unrecognized configuration; reset the drive".
My only option was to try to "repair" the drives...each drive....and I thought, this doesn't "feel" right, like 5 drives are going to go bad at the same time.
So I put on my thinking cap to see if I could figure this out, because it just doesn't make sense that 5 drives would all have an "issue". When just 5 mins earlier (before I started the process) I was saving and using the pool of drives.
Let's see...I was running Windows 10 Enterprise...I'm getting the latest updates (I go with the "Fast Ring" option with the Insiders). I'm booting from a USB drive and Windows 10 Enterprise installs without an issue...hmmm. Do you see it? It took me a second too. "Wait a second! my USB drive is installation from an ISO of Windows 10 Enterprise, and (follow me here folks) my system was originally installed using the same thumb-drive, but by this point would have received the "Anniversary Update" on Aug 2, 2016. Oh, Snap! That means my Storage Space was upgraded without my knowledge. There is something different about about how the Anniversary Update updated the Storage Pool, which made it no longer backward readable to a straight up Windows 10 system!
Let's test this theory. I downloaded the latest ISO of Windows 10 Enterprise-Anniversary Update from my trusty MDSN subscription download page, burnt that to my USB drive, reinstalled my OS. I fired up the Storage Pool console and it was like little Oompa Loompa's had done something inside because everything was back.
So in other words, Windows 10 Anniversary update changes the way that Storage Spaces are used to the point that pre-anniversary versions, can't utilize them anymore...and they didn't warn me?!
So, I guess I have to ask the question of "why"? Why would Microsoft make Windows 10 Anniversary update not recognize a pre-anniversary OS's Storage Space? Usually, OS's and their features are suppose to be somewhat backwards compatible. Yet in this situation not only does this not seem to be the case, but I couldn't find anything regarding this online (and I do consider myself a "Google-Master"). Now my other question is will this be the same issue when upgrading Windows Server 2012R2 to 2016? Anyone? Anyone? Bueller? Bueller?