I like to keep the C partition small so that it can be easily and quickly imaged/backed up. I quite agree on your second point, it would possibly saved me a great deal of hassle if there was just a quick way of setting and checking the default skin directory.
I believe I've solved this and I actually think I've found a bug in Windowblinds. Since I don't have much room on my C: drive, one of the first things I did was move the library folders (public documents, my documents) from C: to D: Now, I did not use any crazy registry hacks or custom installs to move %APPDATA% or anything wild like that, just the standard Microsoft documented procedure for moving the users My Documents folder and the Public documents folder. However, I n
[quote]Control Panel / User Accounts: What's checked; Standard or Administrator?[/quote] Administrator [quote]Also look in Events Viewer / Windows logs. What kind of errors is it throwing?[/quote] Could not see anything relevant. I did fire up the old Sysinternals Process Monitor, bit of a needle in the haystack but I did see this:- RegQueryValue HKCU\Software\Stardock\WindowBlinds\WB5.ini\Wallpaper\SwitcherMode NAME NOT FOUND Also, I found som
The account that was created when I installed Windows, it has the standard Windows 7 admin rights (i.e I still have to confirm with UAC when I install something or make a system change). Out of interest, I tried making a new account. Windowblinds does not work at all under the new account. First time I loaded it it bought up a list of skins but just reverted the desktop back to classic when I applied one. After a reboot Windowblinds just opened up an empty window with no skins to choo
I'm using the same account at the moment for everything.
The file contained 366 lines, each line is a datestamp, followed by Info, CSI, then a hex code, the file looks like this from beginning to end:- 2011-10-25 20:38:34, Info CSI 000002e2 [SR] Beginning Verify and Repair transaction 2011-10-25 20:38:35, Info CSI&nbs
Can't see any instances of "Cannot repair member file" in that log.
No Windowblinds folder in C:\ProgramData on my system. What exactly am I looking for in cbs.log?
Well just tried as CarGuy suggested and no dice, I still can't get Windowblinds and UAC to work together.
Sounds worth a try, thanks, that would be everything in:- C:\Program Files (x86)\Stardock\Object Desktop\WindowBlinds C:\Users\Public\Documents\Stardock\WindowBlinds and any where else? (there's a 3rd folder?)
Yep, e-mail is sent to Stardock, I hope they help me too, I absolutely hate reinstalling my computer and I only did it on Sunday :( It's not just installation UAC protects you, its runtime too. Of course, Sandboxing is one way of providing security. You can have a completely sandboxed OS like an iPhone or iPad, but then there are times when you need to write to the OS, or even perform an administrative task. I don't know, maybe in those instances we can have some sort of promp
The difference being without UAC you are trusting every application you run on your PC to be 100% safe, with UAC you can pick and choose, though of course if you go ahead and click "Yes" for everything you'll still get "pwned" as they say. Yep, my system is completely patched up, latest Nvidia drivers and latest DirectX, I tried several of the stock skins and the problem persists.
Disabling ESET Smart Security did not solve the problem either. UAC's actually very useful if used correctly. Not only does it stop every program having full access to your system, but it makes it possible to run as a limited user without the ball-ache of switching over accounts every time you want to install something or change a system setting. It's made looking after Pc's for the rest of the family much easier in this regard.
sfc /scannow in safe mode found nothing. Reinstalling Windowblinds completely (including deleting the Windowblinds folder) also did not solve the problem. I am going to open a support ticket, I'll also try disabling my antivirus (Eset Smart Security 5). Thanks for all the suggestions.
Hmm, doesn't sound exactly like the same error but similar, I will do the SFC thing in safe mode just to be sure, then try uninstalling/reinstalling and then open a support ticket. This system was only freshly installed on Sunday (23/10/11) though I have installed a lot of software since then. I have not installed any theme-patching tools a-la Vistaglazz or anything like that though. Oh and thanks for everyone's help so far.
Already done sfc /scannow it found no errors. Remember the error only occurs when I apply a Windowblinds skin, it goes away the instant I switch back to Aero (without uninstalling Windowblinds or anything like that).
Absolutely anything that requires elevation via UAC, for example, right clicking on anything and choosing "Run as administrator". It's as if something is cancelling the elevation process as I hear part of the usual "beep" sound and the screen dim for just a split second before the error that appears.
[quote]Doesn't really provide much purpos[/quote] Well I'm not going to get into an argument here but you are absolutely wrong on so many levels with this, UAC is designed as a mechanism to move Windows away from running administrator accounts all the time, the single biggest reason why Windows XP got so many crippling malware infections. There is no way I am risking my system by disabling it. Ok, thanks guys I got the latest version and the problem still persists, eve
Okay I've downloaded directly from Stardock and I've also checked Impulse and enabled "show pre-release versions" and all I can find is build 309, where on earth do I get build 310 from?
[quote]UAC is really a guideline for home users[/quote] If you think that you've fundamentally misunderstood what UAC does and what it is for. Disabling it is a huge backward step for Windows security and is not something I'll be doing. You can boast to me all you like how you never got a virus etc, I know people that drive around without a seatbelt who have never been injured, doesn't mean it's a good idea. [quote]Build 309 has issues. You should go DL B
Brand new clean install of Windows 7 64, just installed Windowblinds and changed to the Sublime skin. Everything seemed to work OK until I fired up a program that needed admin rights, then I get this, the screen goes black for a split second, then a dialogue box appears saying "File system error (65535)". This happens on any program that requires UAC elevation until I switch back to the standard Aero desktop then things start working again. I've run a SFC /scannow in case of corruption an
Hi, I really love Windowblinds, but it really is a PITA at times. One thing that might be useful would be some sort of list of programs that are incompatible, or that need workarounds applying in order to get them working. I've noticed that some skins are less compatible than others too, for instance, Encounter seems to foul things up a lot more often than other, more simple skins. Could we have a thread where people can report their incompatible app, the skin they were us
Done, above post written out of frustration as well, you must understand. I am sure I can live without my Windowblinds skins for a day or two.
Ah I fear its worse than a virus, it's that old demon called DRM again. No viruses according to a full scan with NOD32, I've restored from a system image. This time I was able to uninstall Windowblinds and reinstall it. After I reinstalled it I got "Windowblinds does not appear to be installed correctly on your system". So I clicked to fix and it demanded I activate it again, now I get "Maximum activation requiests from this IP address reached". Great thanks Star
Yeah I had login studio, tried ctrl+alt+del no luck. Thanks for all your suggestions, time to get Acronis going and restore from backup I think. Could this have occured from me installing a Beta Windowblinds perhaps?