3 Replies Latest reply on Jan 23, 2018 6:57 AM by davidg5700

    BSOD after Win10 version upgrade

    davidg5700 Specialist

      In order to upgrade the Win10 version and fix issues on certain machines, I created a provisioning template that reboots the laptop and performs the OS upgrade/refresh form the install media.  I run setup.exe from the installation with the command line strings "/Auto Upgrade /Unattend /Copylogs %SystemDrive%\ProgramData\LANDESK\Log\" as a software distribution package.  These actions are being performed in the system configuration pass.  I created a Provisioning Package referencing the provisioning template to create the distribution task. 


      I pushed this task on about 30 some odd machines and had 25 BSOD's "A required device isn't connected or can't be accessed".  A few were repaired by hitting F9 to choose a different operating system, but most had to be swapped out.  Not a good few days afterward.


      I had previously done this process on about 100 machines prior to this using the install source and manually running the commands.  In order to speed the process of the remaining machines in need, I created the provisioning template to run this.  I often ran into people that said they would reboot their machines before they left, but had done nothing but walked away at the end of the day with all their apps left running.  To combat this, I created the template with the reboot as the first action to overcome this issue. 


      I could never pinpoint what had caused the BSOD's and chalked it up to a massive freakout that hit the VMWare environment that runs the core server on the night that the task was push out the the 30+ machines.  Yesterday, I rolled up another task to upgrade to 1709 in same provisioning template mold.  First test run of it gave me the BSOD.  To test if it were the source install causing this (which was different from the 30+ machines) I copied the install locally and ran it with the same command line.  This went through fine.  The only difference really between the two runs in that there was an initial reboot in the template and the setup was run as the System account, not as a local admin as in the second run. 


      So, since the second run indicated it wasn't an issue with the install source, I tried moving the reboot into the Pre-OS installation pass.  This test ran fine.


      Why would having a reboot action in the same configuration pass in the template cause a BSOD?  This really does not make any sense to me.


      I have attached the working templates and packages and the template that caused the BSOD's initially (Windows 10 1703 Refresh.xtp)

        • 1. Re: BSOD after Win10 version upgrade
          michael.odriscoll SupportEmployee

          Hi David,


          Thanks for posting to the Ivanti Community!


          Sorry that it seems no one has the answer to be able to assist you on this yet.  Did you manage to get any further information on this? Please share anything you deem useful and the community may be able to offer some help.


          If not then please do consider the other ways to engage with us to get assistance:


          • 2. Re: BSOD after Win10 version upgrade
            phoffmann SupportEmployee

            The closest thing I could try recommending here would be running tools like PROCMON in the special native mode for troubleshooting issues like boot up problems. That said, I do NOT know whether it can help with boot-up time BSOD's. That's a very tough time to get useful logging out of the OS, sadly.


            A reboot before the "actual" Provisioning task does make a lot of sense & is usually a part of BKM (specifically because users tend to leave things open, as you discovered, plus it gives Windows a solid chance at writing out a bunch of "Pending File Rename" stuff).


            There's nothing magical about what we do with the reboot per se (it's a call to a Windows shutdown API). You'd think if THAT causes BSOD's then so would/should a regular reboot (again - we're not doing anything special sauce as far as the reboot is concerned).


            Approaching this logically - your first priority is finding out what's going wrong with the OS at boot-up. Whatever information you can pull from the bricked systems - great (does "safe mode" or so work? What about the debug logging mode (which I don't tend to find overly helpful myself usually). Boot-time BSOD's are a massive pain in the back-end due to the pain in extracting information as to WTF is actually happening ... so the options are rather thin on the ground.


            But if you can find out where / why the OS is bricking itself over a humble reboot, that may start with the breadcrumb trail on where this needs to go.


            <And yes, I'm equally headscratching on that one - never seen anything like this in my 20-odd years in the IT industry... >


            Sorry I can't help much.

            • 3. Re: BSOD after Win10 version upgrade
              davidg5700 Specialist

              I am still working on trying to isolate this issue.  One thing that I am testing is not turning off the autoupdate during setup (remove /Autoupdate Disable from the setup command line).  A bit of extra time to ensure that a computer doesn't get jacked up is time well spent.  I'll report back on how that goes.