It's strange that you got the error "Windowblinds was not installed correctly" because Windowblinds was made for all current Windows operating systems. It sounds stupid but did you try running the installer as administrator ? I would recommend using revo uninstaller to uninstall windowblinds then restarting your PC and try installing again. Revo uninstaller will remove any trace in registry and any file associated with Windowblinds (providing it's not a system file of course).

I tried everything, even installing with Kaspersky disabled...nothing changed.

What do you mean " Revo unistaller will remove any trace in registry.." ? I have got Revo Pro , but when I unistall WB first it starts the WB uninstaller, and then appear a window where is said "You need to reboot the pc..." . I close this window and make an "advanced"scan  for all app related files, but only files in Program folder are detected, no registry traces...Is this normal or there is something wrong ? 

I have got the feeling the only way to make WB working could be just reinstalling Windows...if something go wrong in the registry, there is nothig to do, even a system restore is not useful, unless you got a previous full registry backup available..

That's definitely not normal stuff going on.  Maybe before the full wipe, try an sfc scan:

-click Start, in the start search field type 'cmd'. Right-click on the search result and select 'Run as administrator'.
-If UAC is enabled, click 'Continue'
-Type: sfc /scannow
-Wait for the scan to complete (this can take several minutes)
-When the scan has completed, please let us know the result of the scan.

For us visual people:

I was just about to recommend an sfc /scannow procedure, Rosco has lightning fingers xD. Might I ask your current computer setup ?

I know that, I runned 1 time, but it only works for restoring missing or corrupted system files, not for registry entries...Besides, after WB crash I'm running some W7 Visual Style, so if I run sfc /scannow it will restore the patched system files (uxtheme.dll, themeui.dll, themeservice.dll ) and I have to patch them again...But this has got nothing to do with WB, the crash was before installing any VS or patching any file

One thing: every time I uninstall WB with Revo I got for a very short time a black window  same as sfc /scannow one (command prompt)  where is said "Uninstalling WindowBlinds service was stopped..." and something else I had no time to read..

Win 7 Professional SP1 x86

Ah that's fine, That's just WbVista service it's windowblinds service that was being removed. All is normal in that department. Using patched files could cause confliction. If the values don't exist in registry then that's fine also. sfc /scannow will fix any corrupt system files and thus if your registry is errornous then sfc/ scannow will repair this problem. Just my two cents windowblinds is by far superior to VS .

I already runned sfc /scannow and tried reinstalling WB before patching files, but with no results...I can try again, but sfc /scannow doesn't fix registry configuration issue, only restore system files . Anyway, I'll try. 

Well, in general I agree with you, WB is superior to VS. But I can assure you there are some excellent quality VS as well, similar to a MasterSkin WB , though are very, very few . If you like I can provide you 1 or 2 link.. Main point is , instead, there is plenty of great or excellent quality WB 

that's why WB is superior to VS  ( though no any software is needed to install VS..)

In a nutshell: You cannot have WB and VS simultaneously and have WB work. It won't work on an altered .dll file. End of story.

Decide which you want. OR... maybe port that VS into a form WB can use, and stop altering your system files since that voids any MS warranty on their OS.

No. You just have to alter a Windows System file. 

sfc /scannow won't touch your registry.

After deciding which way you want to go (you can't have it both ways), Get CCleaner, or Wise Registry Cleaner (both free) and scan your registry and clean and compact it.

I don't disagree there are some fine visual styles but Windowblinds doesn't require modification of any system file which makes it a lot more secure. If you have links to your favourite visual styles along with author permission I will be more than willing to port them to WB for you.

^

What is VS?

VS = msstyles/Visual Styles 7 - the software which hacks Windows system files to accomodate those skins.

Oh, I think there has been a misunderstanding. I already runned sfc /scannow after WB crash BEFORE installing any VS or patching any system files, and I tried to reinstall WB, but wiyh no results (...not installed correctly..).  Now I tried again, runned sfc / scannow, restored all system files, restarted, cleaned registry , reinstalled WB..no result    After, I even tried to install WB with UAC disabled...nothing.

In my opinion, as I already wrote in a previous post, the only way to make WB working is reinstalling Windows . Something went wrong in registry configuration, and there is no way to solve it, unless I had a full registry bacxkup created before the crash..but I don't. And at the moment I'm not thinking at all about reinstalling OS...I have got too much works stored. 

Of course it could be that the full version works fine, but I have no guarante about..Is there anyone can guarantee the purchased version will work fine?

By the way, do you know about any CorelDRAW Graphics Suite X5 or Corel Painter 12 compatibility issues ( I don't think so, I'm asking just to be sure..) ?

Was there any error message that windowblinds displayed or windows at all ? I use the Pro version I didn't try windowblinds since version 5 (I wasn't old enough to purchase software at the time) So I had to wait . The only difference between pro and trial is just that a trial. You have a limited time to try. I think the installer CNET has is a little bugged as I've saw other people with the same problems. Try getting it from here.

You can reinstall Windows without losing a thing. See here and here for info.

Whether WindowBlinds worked or not before you "patched" your system files is irrelevant.  Patching system files will prevent WindowBlinds from working properly as WindowBlinds is depending on "clean" "un-patched" Windows system files.

A fresh install of the Windows operating system will most likely allow WindowBlinds to install and work.  Any subsequent "re-patching" of Windows system files will not be a wise choice if you wish to continue using WindowBlinds as it's designed to work.

http://windowssecrets.com/top-story/win7s-no-reformat-nondestructive-reinstall/

@Doc: That is where my first link in reply#40 takes you.  Maybe I should have made the links more obvious.

The second is to sevenforums dot com. 

Are you really  sure about that ? How do you know ?

Well, I can tell you this : around from 2007 to 2009 I runned WB 6 on an XP SP3, together with some visual styles as well, and no problem at all. Of course some windows system files were patched ( uxtheme.dll for sure, I think even another 1 or 2 but I don't remember now...) . To switch from a WB skin to a VS - or VS to WB - it was needed just applying first Windows XP default skin ( from WB or from Desktop Properties, it depends what kind of skin was running, WB or VS). Then, once XP default was applied, it was possible to apply any WB skin or any VS, with no any problem.

The reason is very simple : WindowBlinds has got his own SKINNING ENGINE, and for skinning use his own files . Otherwise it is impossible to get everything skinned (taskbar, start menu, windows frame, progress bar, animations...) without no any system files patched !!!!

Do you want a confirm of this (though you should know...) ? Here it is : for example, sometimes I got some WindowBlinds and Pale Moon compatibilty issues, due to a conflict between WB skinning engine and Pale Moon HW acceleration...so I had to add Pale Moon to the WB exclusion list or disable HW acceleration in the browser to get everything working fine. Of course no problem at all with VS , because to apply a VS you don't need to run any kind of skinning engine ( VS works with some Windows system files - plus his own, of course, but that are just graphic modding - WB works with his own skinning engine ).

Well, on Windows XP this is FOR SURE, tested and guaranteed. I don't know about W7, I have to check (I started running some VS on 7 just recently ) but I'm nearly sure it works in the same way . Usually the system files requested to be patched to allow VS working don't interfere at all with WB . If I get WB working (I'll try first on a clean system ) I'll make some test (I can use a virtual machine as well) and I'll let you know.

- @ roflmfaoo -  

The link you posted is for the installer of WB 7.3 build 309 . From CNET you get the WB 7.3 build 310 . I don't know which is better...not always newer means improved..

- @ - Wizard 1956 and DrJBHL -

Thanks for the link about reinstalling Windows. Very interesting...now I got a couple of question : I have got one DVD a Win 7 Professional 32 bit - bootable - with SP1 included, and one with Win 7 Professional 32 bit single installer package - Retail ( no SP1 included ) . The OS originally installed in my PC was with no SP1 included. In case I want to reinstall Windows, which one is better to use ? I don't know the build of these installer  but they are from August 2011. However, I thnk build shoul be not a problem; if the OS is the same - W7 Professional 32 bit - I think original product key will work..am I right? 

About backup :  at the moment Windows backup is disabled, because I'm running Acronis True image 2011 Update 3 (Windows backup disabled means that Windows doesn't make automatically backup; If I want to make a Windows backup I have to make it manually ). To make a complete system backup  - just to be able to restore if something goes wrong - I need a complete Disk (C:)  backup + a complete "System Reserved" partition backup . Is it correct ? With "High Compression" option checked in Acronis backup settings it takes at the moment from 17 to 20 GB (of course I got an Acronis bootable CD and the backup is stored on a different HD )

MOEBI_US  ...throughout the history of stylesxp [patched uxtheme.dll  Visual Styles] essentially each and every successive Service Pack update and/or new version of the MS OS simply BROKE the 'patch' as there was no interest on the part of Microsoft to ensure that did NOT happen as the process [of patching or reverse engineering] was unauthorized and thus 'illegal'.

There was and effectively has never been any TRUE 'product' support for the 'patch'.... though casual users appear to eventually solve whatever the next 'issue' might be but it's a truly inexact science and definitely NOT worth the risk of potentially trashing a work system.

Windowblinds is legitimate software designed to work within the CORRECT environment, not one altered with patches, whatever their source or alleged innoccuity.

Real advice.  Unless you KNOW exactly what you are doing.... AVOID patched software.

The one for that machine. If it's the one without SP1, to do the non-destructive re-install you'll have to uninstall SP1 and reinstall SP1 after you do the re-install. 

I would just like to point out. What you do with your memory space is entirely up to you (reversing software is not illegal) It's illegal to distribute modified software/patches to modify software. This has been a long battle with reverse engineers and software companies for many years. A prime example would be the 1992 Accolade and Sega case .

Not to say that Jafo isn't correct because he is. Microsoft did not endorse the patches or have any affiliation with them nor did they even agree to them being made so in that aspect it was illegal.

Now to get back on topic. MOEBI_US, Try ver. 7.3 build 309 from filehippo and see if the same results occur.

http://www.filehippo.com/download_windowblinds/

I would think the one from Stardock is more updated.

Yeah, Although not every version is guaranteed to work sometimes a roll-back is necessary. That's where I was getting at with this DrJBHL :p

I think build 309 was the one that loaded as Windows Classic on reboot which was fixed with build 310. (I may be wrong, been known to happen)