INTRODUCTION:  This page is a "hidden" page provided for INFORMATION purposes only for other other techs that may be updating their computers to Windows 10.  Please read the disclaimer in the following paragraph.

 

DISCLAIMER:  This page is provided for INFORMATION PURPOSES ONLY.  The Quogue Library makes no warranty claims whatsoever and does not take any responsibility for any potential or real damages that can occur if any of these tech tips are used/applied.

 

UPDATE: 06 SEPTEMBER 2017:    Please read below (labeled ORIGINAL POST) for further details on the history of Windows 10 and Faronics Deep Freeze problems.  But before then, I wanted to add that I updated our workstations to the Creators Update of Windows 10.  After that, when the workstations were rebooted, every second or third reboot cycle would cause the workstation to do a "Automatic Repair" and present a blue screen with two buttons: "Restart" and "Repair".  Repair would not do anything and Restart would restart the computer as normal.     THE PROBLEM is related to the way Deep Freeze addresses the BootStatusPolicy... basically causing Windows 10 to think the boot process failed.

There is a workaround and it's as follows (please remember the Disclaimer above... you proceed at your own risk and there are no warranties or anything provided.  In other words, back up all your computers... do an image of the drive .. BEFORE proceeding if you are unsure.

Workaround to fix the BSOD (Blue Screen of Death): Automatic Repair  when using Faronics Deep Freeze:

1. Set Faronics Deep Freeze to Reboot THAWED (NOT thawed and locked)

2. Once machine is rebooted Thawed, then: Open command prompt in Elevated (Administrator) mode and run the following command - "bcdedit /set {default} bootstatuspolicy ignoreallfailures" 

Type the above command (or copy/paste) everything INSIDE the quotes but NOT the quotes.

3. Reboot machine.

4. Test functions.

5. Reboot AGAIN.

6. Then set Faronics Deep Freeze to Reboot FROZEN.

From that point on, you won't have a BSOD upon reboot.

------------------------------------------------------------------------------------------------

ORIGINAL POST (from late 2016/early 2017):

A little story for all my fellow techs about the trials and tribulations of my upgrading the Quogue Library to Windows 10 Pro for all our staff AND patron computers.... some of the tips in here may help those of you that may wish to make the plunge or if you don't , it may help those who ask you.... and this will be fairly long, and I apologize for length.

 

I've never been one to sit back and wait.  And goodness knows my consultant friend, Kevin, chides me on "diving into the pool before the water is ready" many times.  But after waiting for 5 months and testing Windows 10 on my own staff computer and one patron computer, I decided to take advantage of Microsoft's free upgrade policy to Windows 10 before July 2016 (and our savings by doing this instead of purchasing the program is between $3K and $4K).

 

Before the upgrade, our patron workstations were all HP Small Form Factor 4300 series desktop computers bought in 2013 (Intel Core i3, 8GB RAM, 500GB Western Digital HD) running Windows 7 Professional 64-bit.  Patron workstations had CASSIE (by Librarica) controlling patron access and printing and they had Faronics' Anti-Virus Enterprise and Deep Freeze running to keep them clean and locked.  Patron workstations all log into a standard user account and then each session is controlled by CASSIE.  (So at the first computer in our computer lab, it was set to autoadminlogin as user: lab1   and password: lab1, then once loaded, CASSIE would start and patrons would log in using their barcodes from either our library or any of the suffolk libraries that could be verified through Innovative's API interface at SCLS)  Patrons would end session by clicking the "Exit" button on the CASSIE bar, and the computer would reboot, thereby flushing everything and resetting it since it was locked by DF.

 

Staff workstations were the same, except no Deep Freeze and no CASSIE (except on a select few staff stations that needed to monitor the patrons and/or administer guess passes).

 

Upgrades to Windows 10 were done by the Microsoft Media Creation Tool which creates a bootable Win10 install USB drive.  I made five of these USB drives and upgraded my staff computers first, followed by the patron workstations. 

 

BUT... BEFORE any of this was done, upgrades to the following software (both server side and workstation side) were applied to their latest versions as presented on each vendor's website :  Faronics Core, Deep Freeze, and Anti-Virus (on the server); plus CASSIE Manager (on the server) and CASSIE workstations (each workstation that had CASSIE loaded had to have the old version uninstalled and the new one installed).  

 

USB drive was inserted, and setup.msi was double clicked and the Win 10 upgrade process commenced.

 

Staff computers had a  variety of different software loaded on them and I was originally worried about upgrading.  Luckily, the MS Media Creation Tool will scan the computer first looking for abnormalities and not continue if it runs into a conflict.  Our computers had none.  Staff computers then upgraded to Windows 10 and ran well (I customized them once Win10 was loaded so that the start menu wasn't cluttered with tiles and I turned off all the pesky Privacy invasion stuff that MS added to Win 10).

 

Patron computers were another matter.  This was a LOT of trial an error and for sake of space (since this posting is already TOO long, I will bullet point the things that I came across) things I did or found out:

 

  • Thaw all workstations frozen with Deep Freeze.  Reboot.  Then from Core, uninstall Deep Freeze client BEFORE upgrade to Windows 10.  Because even though Windows 10 will upgrade with a thawed client still on the machine, once it does a registry entry becomes corrupted and every time the frozen workstation reboots, a blue screen "Automatic Repair" comes up.  Thawed it never does.   But by unistalling DF first and then reinstalling it AFTER Win 10 upgrades, the registry is written correctly and NO programs happen whatsoever.

  • Uninstall CASSIE user station BEFORE upgrade to ensure no glitches; reinstall after Win 10 is up and running.

  • On each workstation go into the CASSIE config screen  as Administrator and into the Session Cleanup section and on the right side is the "Running Applications" section.   You MUST add any program (such as your anti-virus, deep freeze (if you use it) and any other program that you always need to run for EACH session.   You just need to type in the file name with extension (so in the case of Faronics' Anti-Virus, the program is:  FAVEAGENT.EXE) and click ADD.    This will keep these programs running for each CASSIE session.  If you don't , CASSIE will terminate these programs.  They improved their aggressiveness in their latest workstation release of 3.7.3.    

    And this is true for Window 7, 8, 8.1, and 10.

  • If you are using CASSIE to generate Cover Pages to indicate which print job belongs to each patron and you have an HP printer using the HP Universal Printer Driver (either PCL 5 or PCL 6) you can NOT use HP's driver after the upgrade to Windows 10, because if you do, you will not get any cover pages any longer.  You must completely REMOVE HP's drivers and then after upgrading to Windows 10, add the printer and use Windows Update and select Microsoft's version of the HP Universal Printer driver.  Everything works smoothly then.

  • Make sure you go into the Windows 10 settings on each workstation and change the Printer Driver behavior.  Windows 10 defaults to " Let Windows manage my printer by making the last used printer the default printer"  Turn it OFF and this will revert the default printer to the way it worked in Win 7. 

  • Windows 10 allows much more customization in their Group Policy than Win 7 did so much that before I used a program called "Startkiller" to remove the start button because Patrons sometimes would click "shut down" and cause the computer to lock out other users until sessions ended.  Now with Win10, you can completely remove the shut down, log off, restart, hibernate commands from users, as well as remove the entire "All Apps" (formerly All Programs) menu... in other words, you can lock it down as tight as you want, or as loose as you want much easier and you don't need a program such as "startkiller" anymore.

  • Go into the Power Settings (in the control panel) and Click on "Choose what the power buttons do" section and then "change settings that are currently unavailable" and UNCHECK the "Turn on Fast Startup (recommended)".  This new Win 10 "fast startup" is an odd hybrid of a hibernation and shutdown mixed together.  If it's left on, then your computers will behave really weirdly and the speed at which it starts "faster" is negligable.

Everything else I customized as I saw fit.

  

 

Finally... DON'T do any upgrading unless you are fully comfortable.  This is all "caveat emptor" and "use at own risk" and all that stuff.   I started small with upgrading one or two workstations out of our many to work out the bugs and that took weeks.  Once they worked, then two to four workstations a day were upgraded slowly over a period of weeks until they were all finished.  That way, if I ever came across something that wasn't right, I didn't take down the whole place.

 

And I can say that after three weeks, all computers are running well.  No problems at all (knock on wood, big time for luck!).  In fact, patrons say that the computers run faster. So that's always a good thing.

 

Thanks!

 

Russ.

Quogue Library IT Coordinator

email (broken down to prevent bots from spamming, just change the "at" to the symbol and the "dot" to an actual dot:)    russ at quoguelibrary dot org

 

 

 

© 2019 by Quogue Library.  This entire site is General Data Protection Regulation (GDPR) compliant.