Bootskin Pro - What Windows files are affected?

Installed on Windows 7, heheh -- need to restore these files

What Windows files are affected by Bootskin Pro?

Out of curiosity I installed Bootskin Pro on Windows 7. As could easily be predicted, it made Windows unbootable.

I didn't mind and didn't care because my plan was to just reinstall Windows in "Upgrade" mode. Until I discovered that "Upgrade" mode won't run unless you're running within the working instance of Windows that you want to "upgrade".

So I installed a fresh Windows 7 on an alternate partition, and now I just want to use it to replace the files on my original Windows 7 partition that were changed by Bootskin Pro.

I'd like to know exactly which files were affected rather than copy/overwrite all files, because I'm concerned about the ACLs (security access control lists) on the files getting mapped to the temporary Win7.

Jon

25,657 views 12 replies
Reply #1 Top

Unfortunately bootskin won't work on all computers, If you install the program and windows wont load, reboot windows into safe mode and then reapply the default windows bootscreen and uninstall bootskin. As for which files are affected by bootskin?, i am not sure but if you drop an email to support@stardock.com i am sure they will be able to get you sorted out. Good luck mate :)

Reply #2 Top

Nimbin you didn't even read what I posted. I installed on Win 7. The computer cold reboots before I even get to an F8 / safe mode option menu.

I thought this was the official Stardock forum? If every serious question had a "send an e-mail to support@" reply, every post here would have it.

Reply #3 Top

I take it you did not read reply #12 of this thread.Link

And no, I believe this is a user based support forum, although  official support does read these posts and reply here.

Reply #4 Top

I wrote a little console application that performs a binary diff between my original Windows 7 Windows directory (after Bootskin corruption) and the new, temporary installation of Windows 7. 

Among the hundreds of different files including obvious things like log files and mini-databases, a couple binaries looked interesting:

  • C:\Windows\system32\imageres.dll
  • C:\Windows\system32\en-US\winload.exe.mui
I'm sure I'm on the right track, will follow up here once I boot back in my original Windows 7 successfully...

Reply #5 Top

Actually, Wizard, reply #12 of that thread was exactly why I chose my words here the way that I did.

+1 Loading…
Reply #6 Top

Well then,good luck to you. It's experienced,knowledgeable beta testers(which certainly leaves me out) that help make products better for all of us. As for me,I'll stick with Vista until Windows7 SP1,at the earliest.

Reply #7 Top

I thought this was the official Stardock forum?
End of quote

 

Nope.

 

And no, I believe this is a user based support forum, although official support does read these posts and reply here.
End of quote

 

Yep.

 

reply #12 of that thread was exactly why I chose my words here the way that I did.
End of quote

 

Just have to know, you see one of Stardocks lead devs post not to, under any circumstance, install bootskin pro on W7 and you felt the need to install to find out why Neil stated what he did.

 

 

 

 

 

 

+1 Loading…
Reply #8 Top

's why I've been doin this for 12 years..

Anyway, still workin on this, I'll post the solution soon enough. If anyone does know the file change list, I'd like to know, but at this point I suspect the BCD itself. (And no, startup repair doesn't find anything.)

Reply #9 Top

Meh. No luck. Only recovery solution I can figure is to format the drive and reinstall Windows 7 and start over.

The route I took was a) install Win 7 on top of the corrupted install. This moves all the old program files and Windows dir to Windows.old. b ) Booting from an alternate Windows partition, restore the Windows.old contents back to the root.

This once worked for me when Vista was installed over XP, but doesn't work with Win 7 over Win 7. There are far too many hidden artificacts (like the BCD, and some directories that will not appear even when 'show hidden files and directories' is enabled) that are not backed up as files into Windows.old. As a result, even the registry hives, including the user's, will be unable to load as though nothing happen. I was able to boot, but I noticed the wrong partition was C: and the system partition was @ D:. Etc.

Etc., etc.

Fun stuff, screwing around like this is. I love bein a geek. (Losing whatever data I had, not so fun.)

Reply #10 Top

Nimbin you didn't even read what I posted. I installed on Win 7. The computer cold reboots before I even get to an F8 / safe mode option menu.

I thought this was the official Stardock forum? If every serious question had a "send an e-mail to support@" reply, every post here would have it.
End of quote

 

next time you ask for help you can kiss my ass then :)

Reply #11 Top

As was previously mentioned -

If you haven't done so already, please email support@stardock.com and start a trouble ticket. They may be able to assist you.

Please remember that this is a request for support from Stardock and the community members and restrict comments to positive feedback.

Reply #12 Top

Yeah, what Neil said in his post pretty much sums it up.  BootSkin Pro currently works specifically with Windows Vista, and will not work with Windows 7 until updated.