Xiaoth

I've been using Start8 on the Windows 10 technical preview for a couple months, up until tonight. Microsoft just released Build 9928 and, while I want to say Start8 is no longer compatible, but after uninstalling Start8 I've found that the reality is that Windows' taskbar with respect to the Start menu and the search functionality is completely borked, and there may be no workaround. Using dual monitors with different native resolutions might be related to the problem. (Wi

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

'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.)

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

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 t

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.

Also BTW, this might be issue in context of my favorite WindowBlinds skins utilizing some WB features. Combined, WFX+WB result in this blank screen.

BTW, Window FX is running on the Windows XP machine (my home PC) that is hosting Remote Desktop service (Terminal Services). It is also running on the Remote Desktop client machine (my work PC), but that's irrelevant.

I frequently access my home PC from work using Remote Desktop, but when I do, if Window FX is running I just get a blank screen and RD eventually just quits. Being a software developer myself, I have thought about putting up a monitor service to watch for Terminal Services activity and automatically kill Window FX, and then sharing it with the community .... but then I thought, heck, this is something that should be fixed in the product, I should just put in a complaint and cross my fingers.<br/