Today [5]

Damn Kari that is a lot of work.

Goes to show, being a Insider is for tough guys.
Going through all that must of increase your intake of your favorite beverage.

Have a question if I may.
Instead of using VM's would booting into a Clone to gather drivers ect.; going on line to gather what ever, work okay. The reason I ask; I don't use VM's because I know little about them or Power Shell.

Jack

Kari said:

Today I'm a happy Insider, at last using build 17074. I fought for four days to get it done, from Friday noon to a few minutes past midnight last night.

First time ever I had this kind of issues, nothing I tried worked. After building several deployment images in Hyper-V, changing this or that, there was always something that didn't work. Either Windows could not be activated, Office could not be activated, NIC, sound and display drivers not working, always something.

Don't want to post my 1,300 words rant here but I blogged the whole ordeal: Insider Build Upgrade Win10.Guru

A tenacious insider geek aren't you @Kari?

Cliff S said:

A tenacious insider geek aren't you @Kari?

Got it fixed just in time for this weeks update to screw it up again.

kado897 said:

Got it fixed just in time for this weeks update to screw it up again.

kado897 said:

Got it fixed just in time for this weeks update to screw it up again.

^^^^ This.

You guys aren't very adventurous are you. Just think of the sense of accomplishment you are missing.

Lol - eh?

Not adventurous?

I differ. I'm very adventurous.

• All clean installs are performed from scratch - no Macrium Reflect HD restore (because I like ot have my browser caches and such as up to date a spossible, and I don't make backups even weekly, forget nightly)
• I run IP builds as my daily driver (no dual boot either)
• I run IP builds of Office on that same machine
• I'm using a CPU that is almost 10 years old, on a motherboard that is 8.
• I regularly test *other* software on these IP builds (both RTM and ßeta versions)
• I haven't clean installed an IP build directly in a long time - I always install the latest RTM and use WU or UUP2ISO generated .ISO to update back to latest IP
• I game regularly on this same daily driver
• I continually benchmark and test driver releases in IP builds for the hardware on my machine

That, and far more.

I have, however, at least for the nonce, stopped playing with VMs - it's simply too time consuming with everything else that I do lol.

The whole no-backup playing with fire thing is probably top of that list, though. I like to live dangerously (and have gotten burned enough to know exactly what I am doing and what I am facing....)

Today my Rocks will be delivered for my (wild life part of the garden) Jack a colleague from work is dropping in to help Dave with them and Im sure Max will help putting them in the right place

Layback Bear said:

Have a question if I may.

Instead of using VM's would booting into a Clone to gather drivers ect.; going on line to gather what ever, work okay. The reason I ask; I don't use VM's because I know little about them or Power Shell.

In my case, I used a Macrium image mounted as a Hyper-V Vm using Macrium viBoot to get drivers because at the moment it was my only available method to export drivers that I knew would work.

However, if you have an up and running Windows 10 installation with no driver issues, the easier way is to use it, export drivers with PowerShell, then inject those drivers to your W10 ISO and use that ISO to re-install. That's how I finally fixed my issues, setting up version 1709 build 16299 on laptop, then when all drivers were updated and working, I exported them to a folder, mounted my custom image and injected those drivers to it.

I can understand that if you do not know PowerShell, it might all sound and look complicated but want to assure you, that really is not true. The whole process is straight forward, following instructions it will work even if you had never done anything with PowerShell or never mounted a Windows image to be serviced.

My suggestion is, read this tutorial really through: DISM - Add or Remove Drivers on an Offline Image Tutorials

It explains the whole process. In Step Two you export current, working drivers to a folder, in Steps Three to Five you mount a Windows image, add exported drivers to it, and unmount Windows image saving (committing) the changes.

In Step Six you then finally create a new Windows 10 ISO, replacing the original install.wim with your new one.

Easy, straight forward, relatively fast.

Kari

We have a big one coming.
In Germany, the train system nationwide has been halted, for safety reasons.
Gust up to 160 KM/H or 100 miles per hour, are expected

Here is what is expected for Bamberg where I live
click to enlarge: