Community Support


Please use this page to ask questions not included in the FAQ for the All in One – System Rescue Toolkit Technician or Lite versions.  I cannot guarantee that I will answer all questions in a timely manner, but as this toolkit grows, we may be able to have more folks chime in with answers.

  • This is a toolkit Q&A support, not general tech support.  If you need help beyond what the toolkit can provide, please seek computer help from a professional technician in your area.
  • Please do not link to or recommend other tools outside of this toolkit when answering questions, including commands built into Windows.  If the toolkit does not provide a solution, please simply say so.
  • Feel free to suggest additions to the toolkit and I will take them into consideration.  Please make sure that tools you suggest support distribution and commercial use or they will be immediately rejected.

157 Replies to “Community Support”

  1. Would 1000% use this for all my needs if I could, except for one very glaring bug I see when using the latest toolkit – the integrated Clonezilla build doesn’t have support for encrypting backups. Is that an implementation problem on your end or just a general problem on non-exclusively Clonezilla builds? Also, is there a way to get it to work on these builds?

    Thanks for making this – it’s helped me out quite a bit this year.

    1. Good to know, Chris.

      I will keep this in mind for the next build.

      I am not sure if encryption on Clonezilla requires a write-able environment in Ubuntu, but that could be something. It could also be a versioning bug in Clonzilla as my build locks all the software versions in at build time.

  2. I really like this ,clean with no bloat ,connects easily to my mobile dongle and uses very lttle memory + s ome useful tools.

    Make a new version that is installable 🙂

    1. I don’t have any plans for install-able or persistent file systems. I get the request often, but it is out of scope of the project and is quite difficult to maintain control over all of the tools as stuff gets updated and changed.

      Also, my file validation will no longer function against a changed/updated environment. Everything gets updated in one fell swoop during a new version release and is tested at great length in many environments to make sure that the release is stable.

      I do not have the resources to maintain a living operating system which is why the use case for my toolkit is “boot it, get in, repair, get out” or “run Windows Autorun tool once”.

    1. Good to know. I can look into this with the next version update. I have been releasing about once per year, so next year’s version should have a 2018 LTS Lubuntu base instead of 2016.

  3. When I try to boot to the liveCD lubuntu, I get the error: “unable to find medium containing live file system”.

    I wrote the ISO to a 128gb USB drive using Rufus.

    Any Thoughts?

    1. Rufus is not the official supported method of creating a USB, you will have to contact the creator of that software to troubleshoot. I have created a tutorial for the official supported USB creation method and also provide prepared USB that can be ordered from the project page.

      For the tutorial covering the official supported USB creation method:
      – Go to the project page:
      – FAQ & Tutorials
      – (Video) How do I make the USB flash drive version?

  4. Hello, i have try to boot from cd and after i choose from the menu i get an error.
    “0.238858 Error Parsing PCC subspaces frpm PCCT” then the lbuntu logo show for like 5min and then the display turn black. Wath can be wrong?

    Best Regards Markus

  5. Strange problem! I’ve created a live USB but on booting from it, it gets past the initial selection and languages screens, loads lubuntu but then asks for a login and password… any ideas why? This is the latest version from your website (2018-01-02). I’ve used a 2017 version previously and that just used to load straight into the Linux GUI after the initial stage.

    1. I get very few of this kind of feedback, like 3 per year. It is usually one of the following cases:
      – Something wrong with the PC during bootup
      – Bad ISO/USB, need to redownload

      I believe the default Lubuntu login is lubuntu/lubuntu.

      1. Thanks for the snappy response! I tried it on another system and seemed to work. Will attempt a re-download and re-image. Thanks once again.

  6. I’m trying to create a super rescue multiboot USB with YUMI. I had issues figuring out the correct distribution to install the ISO with. To save everyone else time, use “Try Unlisted ISO (GRUB Partition 4)”. It worked like a charm

    1. Hello and thank you for checking out my toolkit. This specific question is best left to the maker of the tool nwipe.

      Yes, you can wipe SSDs with traditional wipe methods, such as nwipe, but there are better ways to wipe SSDs. The reason for traditional multi-pass wipe algorithms is because of how traditional spinning disks store data magnetically and there is a physical magnetic trace leftover even after the sector is re-written. SSDs do not store data magnetically and a multi-pass algorithm can unnecessarily thrash the NAND cells.

      You may want to lookup how to use hdparm, TRIM, or ATA Secure Erase for SSDs. Most of those tools are included in my toolkit, however, this Community Support is only about how to use the toolkit itself and not educating people how to fix (or wipe) computers. I can point you to the tools, but I don’t have time to educate the world about how to be a technician, there are schools and certifications for that. 🙂

      Hope that helps point you in the right direction.

  7. Thanks for the toolkit. I just discovered it the other day when looking for an alternative to the live distro including nwipe and SMART data checking that I had been using.

    I have a question about the nwipe version you have chosen to include with the latest release. nwipe has released newer versions up to 0.24 most recently, however you have version 0.17 included in your 2018-01-02 toolkit.

    Here’s the thing, though. I have actually been running on nwipe version 0.14 for years, and it has worked well because 0.14 logs the device serial numbers , whereas version 0.17 does not, nor does 0.24. 0.21 was just broken when I tried it.

    So what I’m trying to figure out is if there is a toolkit like this anywhere that is running the “best” version of nwipe out there. I haven’t tried every version of it yet to determine what I would think that to be, but I can’t work with a version that doesn’t log the device serial numbers. That is a requirement, which is why I’ve been using such an old version for so long.

    If you’re interested in entertaining changing the nwipe version, I would be happy to do some of the leg work by trying each release and giving my own feedback on it. Thank you so much for your time.

    1. Thank you for checking out my toolkit. My toolkit relies on the repositories for the official Ubuntu release of nwipe.

      As of the 2018 toolkit version, the latest LTS version of Ubuntu was 16.04. The best way to go about what you are asking would be to contact the developer of nwipe and ask them for that requirement. Eventually all of the software sources and Linux distros will adopt the changes as they update.

      This may be a good starting point for you:

      1. Haha. That’s the exact page that brought me here, actually. I’ve been participating in some discussions over on their Github project page for a while discussing features and bugs.

        So essantially, whichever version of nwipe is in the latest Ubuntu LTS release will be what you include in AIO-SRT?

        1. Oh yeah, I had one other question. Does your tool have a persistence feature? I’m having a hard time finding that answer anywhere. I was considering trying to change the nwipe version myself on my USB install, but if I can’t save the changes to the system afterward, that would be pointless.

          Thanks again.

          1. Lots of good questions, hopefully this answers them for ya:

            The toolkit doesn’t support persistence at this time since it is pre-packed and loaded using the squash.fs filesystem. There are no plans to officially support persistence, however Ubuntu has a great guide for getting it setup.

            Persistence would make things like file integrity checking on both the boot menu as well as Windows Autorun difficult. One of the integrity checks (the cloud icon one) for Windows Autorun pulls down the latest file checksums for the ISO file as originally published and released from the web. Also, the “Removable Device” format using FAT32 doesn’t officially support multi-partition USB drives as far as I am aware.

            Also, yes, for the sake of my sanity of verifying bugs for every single piece of software, I choose the most recent stable versions as of the ISO preparation date. Ubuntu does a great job with LTS versions of keeping bugs to a minimum so that apps work in as many configurations as possible as stable as possible. With the Windows apps, I update them on a final push before publishing a toolkit version.

  8. Hello, I am new to ISO’s so forgive me for the learning curve. I successfully created the AiO-SRT flash drive with no problem. I also want to make a live CD but not sure how to proceed. I have the AiO-SRT iso on my computer. What are the next steps to create a bootable CD and then install AiO-SRT on it? Thanks in advance.

    1. Thank you for checking out my toolkit. You may want to Google “Burn ISO to CD”.

      I think most recent versions of Windows give you a burn to disc option when you right click on the ISO.

  9. There is a problem with the USB drivers loading. I get to the desktop, but the mouse & keyboard do not respond. I’m booting from a CD.
    I see during booting a ton of USB5/4 device descriptor & read/64 error -32 lines stating unable to enumerate, not accepting address xxx

    I have run into these errors with 1 or 2 other bootable programs, thou most bootable programs work fine.

    I have a UEFI MB, but I’m running it in BIOS mode if that matters.

    1. If you are having issues with multiple boot environments, I might look into the underlying hardware more than a specific toolkit. It sounds like more environments than just my toolkit are complaining about USB on your system.

      This is a strange issue and I have not personally encountered this before. It is possible if the PC (and/or USB chipset) is newer than 2016 that there’s something not quite right with the USB support in Lubuntu 16.04.3 LTS (or other boot environments you mentioned).

      By the time I release my next version, 18.04 Ubuntu LTS should be released and we will have a newer platform for the LiveCD environment. I refuse to use anything other than LTS for production and serious repair tools.

      I am curious to see if anyone else reports or replies with this kind of issue. Thanks for letting me know!

  10. Hi, first of all, thank you for this useful tool. I´ve used it in quite a few PCs with greats results. However, I recently got an issue in an old notebook, when I try to run it from a live USB the following message comes up:
    “This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot”.
    The PC has an Intel Atom N270, 32 bit CPU, 2GB of RAM, and is running Windows 7 Ultimate as primary OS. Is there any solution to this problem?

  11. Hello — Do you recommend running your toolkit (I have the lite version) as a part of routine maintenance, or is it solely for troubleshooting problems? My antivirus (Microsoft Security Essentials) runs once a day, and about once a week I run Malwarebytes and BleachBit. Would it be useful to add in your System Rescue kit to my routine? I’m running Win7/64 on an aging laptop.

    1. None of the utilities in my toolkit are so aggressive as to cause issues if run too often. (No registry “cleaners” for example).

      For a well maintained system, it might be useful to run once per year or every 6 months. It’s really designed as a stop gap when deciding if a technician needs to get involved with the system repair. Run the toolkit first, if there’s still issues, definitely call a technician because it does almost all of the basics.

      I typically do a tune-up to my PC when I “start to feel it”. Sluggish, taking longer to boot or load apps, etc. For most of my paying clients, this lands in the every 6-12 months range.

  12. Boot problems on my Dell XPS 15. Start to boot, but then hangs with the Lubuntu logo. I fixed my problem with another Tool disc, but I just though that you might want to know.

    1. Thanks for letting me know. Do you know if you were booting UEFI or BIOS? Also CD or USB?

      To prevent issues with burning/creating bad media here are some steps I use when I build official discs that people order from me:
      – Use known good media for CDs (Verbatim, Memorex, etc). Some cheap media will not recognize in all CD/DVD drives.
      – Verify disc after burning, most burning software has this option, but not turned on by default
      – Use known good media for USBs (SanDisk, PNY, Transcend, Kingston, etc). Cheap USBs are known to cause I/O issues
      – Verify integrity of USB creation from the General tab in Autorun after creating USB

    1. Are you asking for free software you are using to not be credited back to the software creator? Think about it.

      There is a small possibility that I might offer a paid branded option for IT shops out there to rebrand my software and drop their own links, website information, etc. I have no plans at the moment to begin that process though.

      Getting my name, website, and information out there is one of the ways I am allowing people to use my software for free.

  13. Great project, thanks for all your work on this. I’m wondering how difficult it would be to include support for bitlocker encrypted drives via dislocker? Likely you’ve already considered modifying the live CD to either have some persistence or include the libraries by default, I’m trying to wade through the documentation to see how to include by default. I can get drives mounted and unencrypted but have to install several libraries to get dislocker compiled the first time booting on new machine. Thanks again for your efforts and any hints would be appreciated!

    1. I have looked into dislocker before. While I am able to use linux and script just fine, the goal of my toolkit is simplicity and generalization for the masses. There are just too many hacky steps to include the utility in LiveCD when Windows already includes utilities to work with BitLocker natively on the installation media.

      BitLocker is just enough of an outlying case that I can’t really justify putting it on without something polished to make it useful for the masses. Most corporations that rely on bitlocker should also have an in-house procedure for working with bitlocker encryption and recovery.

      It’s one of those tools that if you need it, you search it out specifically, and you plan for the “just in case” scenario. Also, backups are important. Any data recovery specialist shops that deal with this also have in-house tools and wouldn’t reach for my generalized toolkit, I hope.

      This was almost the case with chntpw. It’s a bit hacky to use, which is fine for me, but resetting Windows passwords is way more common than BitLocker recovery without backups.

  14. I may be missing something or looking in the wrong place (highly likely!) but I have been unable to find a temperature monitor. A colleague advised that his laptop seems to be overheating and the fan kicks in (as it should) during normal operation but he says it is like a jet taking off. I have run the CPU stress test application for 15 or 20 minutes and have been unable to get the fan to make the fan make as much noise as he says it does. Whilst the widgets on the right hand side of the screen tell me how much load the CPU is experiencing, it would be helpful to have a temperature monitor so that I can show him that everything is within normal limits. Are there any plans to implement such a feature or is this one that has been considered and disregarded? Kudos on useful piece of kit though.

    1. On the LiveCD part of the 2017 toolkit version the temp gauge needed to be added to the panel manually. I made a tutorial about how to diagnose PCs with my toolkit that shows how to do this. Windows Autorun CPU stress test automatically runs HWMonitor which shows gauges.

      Starting with 2018 version, “CPU Stress Test” is renamed “mprime” and autoruns a sensors monitor on the LiveCD portion. HWMonitor is still used during Prime95 on the Autorun side. It sounds like you are running the older version.

  15. I see there is a checkbox next to the automatic mode under “autoFIX”. How does one save this setting to “off” so that it doesnt run automatically?

    Ive unchecked it and closed and reopened the program but it reverts back to default.

    1. Just in case anyone else is wondering as well. The toolkit customization only works with writable media.

      autoFIX customization is also only saved when it is run. So if you select options, close and reopen, it will just load last settings. You can also look in the custom.ini file inside “extras\custom” on the toolkit to see how the options are stored.

  16. I just downloaded the ISO of the all in one toolkit and burned it to a CD for testing. When I insert the CD into a Windows 7 machine and double-click on AIO-SRT.exe, I get a warning that the file contains a virus. The exact message is: “Operation did not complete successfully because the file contains a virus.” I am now concerned about evaluating the toolkit further. Anti-virus software installed is Avast Business CloudCare (formerly AVG CloudCare). Any thoughts?

    1. With any new software, not just mine, I would recommend evaluation on a non-critical PC. This can be done in a virtual machine or “project PC”.

      To address your question directly, my toolkit doesn’t have the funds to pay for whitelisting for all antivirus software out there, so it relies on reports of false positive from the community of each antivirus. This version was just released this past week, so it probably doesn’t have that “false positive” flagging done yet. I just had a campaign to get unblocked by MalwareBytes, which was successful thanks to the toolkit community.

      If it helps, you can check out some of the reviews on my references page written by other folks in many languages:

      Some notable places off the top of my head that reference the toolkit include: LifeHacker, MajorGeeks, GHacks, Navigaweb, Chip Online, Hitek, TheWindowsClub.

      I will update my FAQ entry on antivirus alerts for everyone.

  17. It appears Microsoft’s ‘Create a Recovery Drive’ is the bane of my existence. I was able to run it normally on one PC, had a whole bunch of problems on another (but finally got it to work), now the 3rd one has me stymied. The message I get is “We can’t create a recovery drive on this PC. Some required files are missing. To troubleshoot problems when your PC can’t start, use your Windows installation disc or media.”

    I’ve run Windows Update, SFC and DISM and they didn’t do anything to fix this issue. Windows, of course, gives me no clue as to which ‘required files’ are missing and the PC otherwise works fine. It’s a Cyperpower PC with AMD Ryzen 1700x processor on an MSI Bazooka motherboard. Windows 10 Home was originally on the HDD, but has been installed on a SSD and runs from there.

    I note there are 3rd party utilities to create bootable Windows drives, but I’m leery of using one without a recommendation or reference from a trusted source.

    Here are my questions:

    1) Does your AIO-SRT have a utility to create a bootable USB flash drive?

    2) If not, is there a 3rd party utility you’d recommend?

    Thanks in advance.

    1. My toolkit can create a bootable USB version of itself (Lubuntu 16.04 LiveCD base), and contains a program called Rufus that can create bootable USBs from ISOs. Although, I think your question is about creating bootable Windows environments which I do not have the legal rights to, nor does pretty much anyone else that I know of except Microsoft.

      Missing Microsoft Windows core files can’t (and shouldn’t) come from anywhere else except Microsoft Windows installation media, otherwise you are right to be skeptical of “alternative” files not coming from official Microsoft sources. There are no utilities that I know of that can fabricate or replace missing core Windows files except official Microsoft Windows installation media.

      My toolkit’s live environment can be used to attempt data recovery or transfer data in the event of a core Windows installation failure, but if you don’t know what you are doing, I highly recommend using a data recovery specialist if you value the data at all. It sounds like your system is still running, however. Keep good backups!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.