6 Replies Latest reply on Oct 29, 2010 3:23 PM by hindsight

    SafeBoot client not activated

      After the weekend,  had 5 devices come up with 'No Operating system found'.  Using WinTechtools to try to restore the MBR,  we get the message the above message.  Cannot authenticate to teh device,  only authorize.  Therefore we cannot do any work on the device.  Suspect the issues with Microsoft patch MS10-015 at the core,  but not sure what malware it is or what it did to the MBR.   ANy ideas for getting the MBR corrected so we can at least get on the device to do more troubleshooting?

       

      Thanks in Advance.

       

      -Troy Woods

        • 1. Re: SafeBoot client not activated

          you can't really correct the SBR - your best bet would be to manually decrypt a machine with WinTech/SafeTech, then do "Restore original MBR".

           

          make sure you grab a copy of the existing MBR first though.

          1 of 1 people found this helpful
          • 2. Re: SafeBoot client not activated

            I would try to use WinTech CD and utility first, to see if encrypted disk is mountable. If it is, I would make disk image to use it for troubleshooting and also as a data backup.

            • 3. Re: SafeBoot client not activated

              Please note - This posting only applies to SafeBoot version 5.x versions

               

              Problem Statement:

               

               

              It is possible for a system with SafeBoot installed to have its MBR corrupted. When this happens, a system will typically show the error, “Error loading operating system. Missing operating system.”, during boot. This condition can also be brought about by attempting to initiate an image backup of the hard drive using an application such as Ghost or Acronis from within Windows.

              -

               

              If the condition started occurring starting with the first reboot after attempting to initiate an image backup, do not perform the procedure in this document.

              Subsequently, when a system in this state is booted to a Bart PE CD with SafeBoot Tools included, and Authentication from SBFS is attempted, the error, “Error code: 0xe0050001 - SafeBoot Client not activated” is shown.

               

               

               

              There is a solution for this condition, but it must be administered very carefully and completely.

               

              Prerequisites:

               

               

               

              A. The SDB file for the machine must be obtained prior to administering this solution.

              B. Note that several steps in this procedure will have slightly different wording depending on which version of the support tools are being used (e.g. Restore SafeBoot MBR vs Restore EEPC MBR).

               

              Procedure:

              1. Attach a USB drive with the machine specific SDB file in the root directory prior to booting.

               

               

              2. Boot to a Bart PE CD with SafeBoot Tools included

               

               

               

              and launch the ‘SafeTech for Windows' application

               

               

               

              3. When SafeTech for Windows is launched you will be prompted for the Authorization code. This code changes every day.

              The TechCode for DD/MM/YY is '####'

              The TechCode for DD/MM/YY is '####'

              The TechCode for DD/MM/YY is '####'

               

              4. Next choose ‘Disk Information’ from the ‘Disk’ menu.

               

              5. In the ‘Disk Information’ window:

              a. Expand the partitions and identify the one with Drive Letter C:

               

               

               

               

              b. Take note of the ‘Partition Start Sector’ and ‘Partition End Sector’ for the Partition with Drive Letter C. You only need to capture the numbers after the leading 0’s (e.g. 0000000063 can simply be noted as 63).

               

               

               

               

              c. Close the ‘Disk Information’ window.

               

               

               

              6. Choose ‘Open Workspace’ from the ‘Workspace’ menu.

               

              7. Next select ‘Load From Sectors’ from the ‘Workspace’ menu.

               

               

               

              8. Leave the ‘Disk’ set to ‘Disk 0’. In the ‘Start Sector’ field input the Partition C Start Sector you noted previously. Leave the ‘Sector Count’ field set to 1 and click the ‘OK’ button.

               

              9. Next we need to determine the state of the drive. We can do this by looking at the far right section of the ‘Workspace’ with the Start Sector of Drive C loaded.

               

               

               

              10. Here are examples of the far right section of the Workspace for drives in various states:

              -SafeBoot Encrypted - Random characters with no apparent words or patterns.

              -Unencrypted - You can clearly see NTFS near the top and the message “A disk read error occurred…” near the bottom of the column.

               

              11. If we confirm by the state of the Start Sector of Drive C that the machine is indeed SafeBoot Encrypted, we can proceed with the rest of the steps. If it is not SafeBoot encrypted, we should not proceed any further.

               

              12. Leave the Workspace open and choose ‘Authenticate from Database’ from the SafeBoot or Wintech menu.

               

              13. Browse to the location of the provided machine specific SDB file and choose ‘Open’.

               

              14. You will then be prompted with the ‘Select Machine’ dialog box. There should only be one machine, so simply click ‘OK’ when prompted.

               

              15. Once you are ‘Authenticated’ you can verify the status from the Information Bar at the bottom of the window.

               

               

               

               

               

               

              16. With the Workspace still open to the Start Sector of Drive C, choose ‘Decrypt Workspace’ from the ‘Workspace’ menu.

               

              17. If the SDB file has the right key to decrypt the workspace, the workspace will now be seen in a decrypted state. You should be able to clearly see “NTFS” near the top and the message “A disk read error occurred…” near the bottom of the far right section.

               

              18. If the Workspace does not appear in a decrypted state, do not continue. If it does appear decrypted, you may proceed with the following steps.

               

               

              19. Choose ‘Restore SafeBoot MBR’ or ‘Restore EEPC MBR’ from the ‘Disk’ menu.

               

              20. Select ‘Yes’ when prompted with the message, “This function will overwrite the Master Boot Record. Continue?”

               

              21.

               

               

              You should then be prompted with a success confirmation. Click ‘OK’.

               

              22. Close the ‘SafeTech for Windows’ application and shutdown the system.

               

              23. Boot the system normally to determine if it boots as it did before the ‘Missing Operating System’ condition developed.

                        -

               

               

              In some cases, the system will instead present a SafeBoot 92H error. This error can typically be resolved by performing an emergency boot. Boot to a BartPE CD with SafeBoot Tools included, back up the user’s data (for safety's sake) and then performing an Emergency Boot while authenticated from the machine specific SDB file and booted to a SafeTech CD.

               

              24. The procedure is now complete.

               

               

               

              I have been dealing with more and more cases such as this. There seems to be no end in site... I'd like some help knowing what all the possible causes are that result in a standard windows MBR being put in place of the SafeBoot MBR. In each case, the users report that no patching or updates were taking place prior to the reboot that resulted in the "Missing Operating System" message.

               

              Good luck!

               

               

               

               

               

               

               

               

              Message was edited by: StuManChu on 3/4/10 6:03:29 PM CST
              • 4. Re: SafeBoot client not activated

                In those case was EEPC pre-boot present, then OS error or NO EEPC pre-boot screen at all?

                • 5. Re: SafeBoot client not activated
                  18. If the Workspace does not appear in a decrypted state, do not continue. If it does appear decrypted, you may proceed with the following steps

                   

                  Ok, so what if the drive still DOES appear to still be in an encrypted state?

                      driveinfo.JPG

                   

                   

                  workspace.JPG

                   

                   

                  And... furthermore what if I replaced the MBR with the "Restore EEPC MBR" option. (I hadn't found this post until after I'd done it)

                   

                  The original problem was the machine immediately after post would go to a flashing  "_" in the upper left, instead of the MEE login screen.

                  After replacing the MBR with the Restore EEPC MBR option it now says Operating system not found.

                  I had used authenticate from database with the user's SDB file from a thumb drive to get Authenticated in Wintech. 5.1.7.0

                   

                   

                  Message was edited by: hindsight on 10/29/10 3:21:44 PM CDT

                   

                   

                  Message was edited by: hindsight on 10/29/10 3:22:38 PM CDT

                   

                   

                  Message was edited by: hindsight on 10/29/10 3:23:48 PM CDT
                  • 6. Re: SafeBoot client not activated

                    Please post your case in a separate thread.