Announcing Windows 10 Insider Preview Build 16215 PC + 15222 Mobile Insider

f14tomcat said:

Let me explain some experience concerning MS installs and device drivers. I have a NVMe SSD drive on this system. It's in a eSATA slot, not SATA 0. If I go to do a clean install from a thumb drive, properly prepared with the MS ISO, it will fail to see what we would call "drive 0". Sees all others, not the first one, the NVMe SSD. In order to get it to see the drive, I have to include the Intel drivers for that SSD on the thumb, and load them manually. Then it will see the "C" drive and allow me to choose where to install.

I'm using that as an example of a missing driver in a MS official ISO installation package causing issues with the process. The same exact problem when using Kyhi's Rescue media. I have to "Inject" those drivers into his package (the part that comes from the official MS ADK) in the .wim file on the thumb, then when I boot his Rescue thumb, all the progs will see the "C" drive. If I don't', the drive is invisible.

.

In my case I have an M.2 PCIe NVMe(which does NOT show up in BIOS in SATA mode), and only need to switch my BIOS temporarily from SATA to RAID(chipset contains the needed IRST drivers, but needs to be set to RAID to use them) to install Win10(then the disk also will show up in BIOS).
PCIe NVMe is a SCSI disk and Win10 has basic NVMe drivers(later I install the Samsung ones). After install I can go back to BIOS and switch to SATA if I want.

from here


or from here
By the way, just using RAID drivers, without setting a RAID up, works just fine, you then don't need NVMe drivers(already tested it once).

But Dick, just to expand on what you need to do:

For F6 driver injection: http://download.intel.com/support/ch...user_guide.pdf (start at 5.2)

5.2 F6 Installation Method

The F6 installation method requires a 3.5” diskette with the driver files.

5.2.1 Automatic F6 Diskette Creation

To automatically create a diskette that contains the files needed during the F6 installation process, follow these steps:

1. Download the latest F6 Driver Diskette utility from Download Center: Downloads for Intel® Rapid Storage Technology (Intel® RST) 2. Run the .EXE file. 3. Follow all on-screen prompts.

Note: Choose either the 32-bit or the 64-bit version, depending on your operating system.

5.2.2 Manual F6 Diskette Creation

To manually create a diskette that contains the files needed during the F6 installation process, follow these steps:

1. Download the Intel® Rapid Storage Technology and save it to your local drive (or use the CD shipped with your motherboard which contains the Intel® Rapid Storage Technology). Note: The Intel® Rapid


Storage Technology can be downloaded from Download Center at Downloads for Intel® Rapid Storage Technology (Intel® RST)

2. Extract the driver files at the command prompt by running the following command: {filename} –A -P {path} Example: IATA_CD_10.6.0.1022.EXE –A –P C:\TEMP

3. The following directory structure will be created:

\Drivers \x32 \x64

4. Copy the IAAHCI.CAT, IAACHI.INF, IASTOR.CAT, IASTOR.INF, IASTOR.SYS, and TXTSETUP.OEM files to the root directory of a diskette.

Note: If the system has a 32-bit processor, copy the files found in the \x32 folder; if the system has a 64-bit processor, copy the files found in the \x64 folder.


5.2.3 F6 Installation Steps

To install the Intel® Rapid Storage Technology driver using the F6 installation method, complete the following steps:

1. Press F6 at the beginning of Windows setup when prompted in the status line with the „Press F6 if you need to install a third party SCSI or RAID driver‟ message.



2. After pressing F6, nothing will happen immediately; setup will temporarily continue loading drivers and then you will be prompted with a screen to load support for mass storage device(s). Press S to „Specify Additional Device‟.



3. Enter> key. Refer to the Automatic F6 Diskette Creation section above for instructions.



4. Select the RAID or AHCI controller entry that corresponds to your BIOS setup and press Enter. Note: Not all available selections may appear in the list; use the up and down arrow keys to see additional options.


5. Press Enter to confirm.

Windows setup will now continue. Leave the diskette in the diskette drive until the system reboots itself because Windows setup will need to copy the files again from the diskette. After Windows setup has copied these files again, remove the diskette so that Windows setup can reboot as needed.

II'm doing a full disk backup image using AOEMI Backupper Pro. I'll admit that 215 rattled me a little and I don't want to go through the exercise of re-installing my triple boot again especially as Windows 10 is installed on the second partition so if I install from an ISO I need to run bcdedit on the Windows Server 2016 OS on the first partition. I have gone through a few upgrades which worked fine in the multiboot environment so my tolerance level is low. I am (quite successfully) running 87 non MS programs. Here's hoping for a better IP.

HippsieGypsie said:

Anyone know how many machines and OEMs/MoBo types MS would test installs on? Surely they must have labs for that, yes? OEMs as well?

Strictly and technically speaking, there's no such thing as motherboard for instance, just a bunch of parts mounted on one board governed by BIOS. An OS developer has to worry only about parts of the system and test on those parts. Processor, all Skylake processors, for instance, need only one driver, same goes for a chipset, sound controller (CODEC chip), IO controller, WiFi and/or network chip etc. Ready made, brand name desktops, laptops etc. are also just a collection of those parts and as far as OS is concerned only BIOS distinguishes them. As manufacturer's are supplying drivers and support those kinds of computers are in practical limbo. Manufacturer's can't be held responsible for third party SW including OS (eventually only OS and SW supplied with the computer and left in original state) and OS and SW developers can't be responsible for any changes OEM computer manufacturers make or any errors their drivers may cause.
Just some of reasons I don't like OEM computers.

martyfelker said:

"Apology build" does sound good. I wonder if Dona will say anything about why the team released a build that they knew had numerous problems. Anyway I learned a bit about my backup and imaging solfware.

I would call it the "Get down and grovel" build. This build is such a disaster, they have probably lost a significant portion of Insiders who will not use Fast Ring any more.

Sure we have to expect the unexpected, especially on new features, but it is still a REASONABLE expectation that it installs ok and things that work ok on old build will (mostly) work on new build.

I personally think MS should step back and not do any new development for a couple of builds but fix all the major issues identfied so far (possibly as a series of updates to 16125?).

Then they should release an iso so users CAN update or clean install.

I have had issues using iso created for 16125 as I cannot boot from it!

MS was under pressure to release a new build, look no further from our forum although methinks they are still bungling this UUP and it's the worst part of whole update system. That's the reason my update failed. Everything was downloaded right and everything works after I used ISO made out of this DL. Installed from it without a hitch and no bad drivers or unusual problems.

As someone who has a perfectly running Updated 16125.....only fault found being an AMD driver needed updating.

Old rescue methods such as creating ISO,s.....system backups etc seem to be no longer possible on this version.....the only viable way being UUP......could this be a new direction security wise taken by M$.?

dencal said:

As someone who has a perfectly running Updated 16125.....only fault found being an AMD driver needed updating.

Old rescue methods such as creating ISO,s.....system backups etc seem to be no longer possible on this version.....the only viable way being UUP......could this be a new direction security wise taken by M$.?

I created and used ISO from this build, it's UUP that made me a problem.

cereberus said:

I would call it the "Get down and grovel" build. This build is such a disaster, they have probably lost a significant portion of Insiders who will not use Fast Ring any more.

Sure we have to expect the unexpected, especially on new features, but it is still a REASONABLE expectation that it installs ok and things that work ok on old build will (mostly) work on new build.

I personally think MS should step back and not do any new development for a couple of builds but fix all the major issues identfied so far (possibly as a series of updates to 16125?).

Then they should release an iso so users CAN update or clean install.

I have had issues using iso created for 16125 as I cannot boot from it!

I assume you mean 16215. I agree. I am wondering why MS cannot release (I assume they could produce) an ISO you could boot from that would update an earlier build already installed and working on a HD? They would be such a pleasure. What's the downside??

martyfelker said:

I assume you mean 16215. I agree. I am wondering why MS cannot release (I assume they could produce) an ISO you could boot from that would update an earlier build already installed and working on a HD? They would be such a pleasure. What's the downside??

Downside ? Not many would use UUP which obviously needs a lot more work but couldn't be tested if everybody used ISO or even ESD.

If you are having problems, when using the feedback hub, don't forget the recording feature.