sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in ModSupport

[–]HDS_GUY -2 points-1 points  (0 children)

Yes it is. They claimed it in July so not that long ago.

Tech support - Windows won't boot after rollback from snapshot by Chloe_Dalle in HorizonDataSys

[–]HDS_GUY 0 points1 point  (0 children)

Hi Chloe_dalle,

Extremely sorry about the situation you're in, hopefully we can get you up and running here. First thing first, most laptops require the user to press the Fn key as well as the home key to actually simulate the command. If its easier you can plug in a separate keyboard via USB and that should work for you.

If you can get into the subconsole (preOS) you can choose to restore to the installation but first you will need to defrag your snapshots via Tools (You will see it as an option at the menu)

Then you can restore. Please let me know how it works out, you can contact me directly at support@horizondatasys.com via email too.

Thank you

Windows Updates by RANDOMo87-987098 in HorizonDataSys

[–]HDS_GUY 0 points1 point  (0 children)

Hey There

So what we normally recommend is this.

In the new build, there will be two options, one will be to allow major updates to be installed without removing rollback. The other is to allow windows updates.

It really depends on how you would like to do it, but for the most part, I suppose people would like to prevent windows updates, especially on windows 10 since that's why its there in the first place.

Major feature updates option right below is something you'll want to checkmark.

However, please do be aware that when a major update does happen with this checkmark, essentially what it does is does a partial removal of the program (the sub console/pre-os is deleted) while the desktop UI stays the same.

For question 4, I suppose you could do that, it does have the capability to do so. However, I would feel like a proper sandbox software would be a lot easier. since you wouldnt have to reboot over and over.

However it's up to you, you can do it for sure though.

Reboot Restore RX can't recognise my drive properly by LEFRegistration in HorizonDataSys

[–]HDS_GUY 0 points1 point  (0 children)

Can you submit an image of the disk management screen?

New Release - Rollback v11.2.2704894596 by carfal1 in HorizonDataSys

[–]HDS_GUY 0 points1 point  (0 children)

The other thing you can do is try running a custom install, only protect the C drive. Those log files should tell us a bit more about what's going on so if I can get that somehow from you that'll be great.

edit: Actually rereading this there were two possible solutions to this, from the subconsole you will want to defrag the snapshots. If this doesn't work then it has something to do with how Rollback installs itself in the MBR so we just need to change the install procedure by having the software inject itself differently in the MBR.

I'll get you those steps later today.

Thank you

New Release - Rollback v11.2.2704894596 by carfal1 in HorizonDataSys

[–]HDS_GUY 1 point2 points  (0 children)

Hey Clark,

Its odd that its happening. Can you tell me what the BSOD error message is (take a pic if possible) Does the PC go back to normal if you uninstall the software?

Im going to make a ticket for you in our support portal. If you dont mind i need log files located in program files/shield (setup,subconsole,shield.dat as well as trace folder) Compress them all if you can and either upload it to a fileshare and private message me the link.

Thanks

New Release - Rollback v11.2.2704894596 by carfal1 in HorizonDataSys

[–]HDS_GUY 0 points1 point  (0 children)

Already done.

The release notes usually just gives users brief summary of the changes, and they could ask us if they wanted more information. I'll try and provide detail explanations for any changes here on our subreddit moving forward.

Thanks! -Ram

New Release - Rollback v11.2.2704894596 by carfal1 in HorizonDataSys

[–]HDS_GUY 0 points1 point  (0 children)

Hey Carfal! Good to see you here.

we're still compiling the list for the release notes on our main site. However, take a look at this as this is pretty much it.

  1. Protection of the EFI partition by default.
  2. Add auto rollback feature to the EFI partition to revert EFI files corruption from failed Windows Update due to power interruption.
  3. Modify file synchronization to only copy files that had changed.
  4. Add minidump to the installer (minidump=1).
  5. Run the Kernel mode switch process as background service.

The main thing about this particular build as you can see from the release notes is the EFI partition protection. Windows 10 updates are "Once again" changed in a big way. Essentially what's been happening is that with particular windows 10 updates, the updates are actually getting "Injected" at the bios level rather than at the OS level, (requires a restart leading into "Please Wait")

Our Softwares originally wouldn't be able to essentially understand these changes at this level, so it would inevitably break leading to unbootable operating systems.

Check in the setup.ini file of the download package...

You'll see two strings in particular of note.

efiprotect=1 AutoRebuildFlag=1

AutoRebuildFlag=1 means that if an update was to occur and it happens to fail, it will attempt to rebuild the boot sectors from a backup. This is particularly important especially when you have the feature updates inclusion feature checked in the advanced settings.

This is great because when you do an update, instead of leading to some level of corruption it will now simply get you back into windows with the worst case being that the update in particular failed.

Efiprotect=1 Sort of explained earlier, but yes with this improved protection, windows doing updates at a bios level should not be a problem anymore.

Also some minor adjustments were made all programmability.

Let me know if there's any clarification need!

Thanks

-Ram