Recommended Posts

i find when i apply a windowblinds skin it will skin applications but not dialog windows, explorer windows, or the taskbar

i tried uninstalling/reinstalling several times but this problem hasn't gone away since i put on SP2 i think (not sure if that's the cause)

in fact i dont even get the windowblinds appearance tab - i just get the normal one

whats going on?

EDIT: using version 4.4

Link to comment
https://www.neowin.net/forum/topic/257415-windowblinds-doesnt-skin-properly/
Share on other sites

  • 2 weeks later...
What happens if you try this?

regsvr32 "C:\Program Files\Stardock\Object Desktop\WindowBlinds\wbui.dll"

585109646[/snapback]

It states: LoadLibrary("C;\Program Files]Stardock\Object desktop\WindowBlinds\wbui.dll") failed - The specified module could not be found.

Now what?

"C;\Program Files]"

Is that how you typed it in? It's supposed to be C:\Program Files\

It's got to be a colon, not a semicolon. And a backslash, not right bracket.

585198356[/snapback]

Nope, those are typo-errors. Excusez moi.

Uninstalled WB, deleted directory. Cleaned registry with Regseeker, re-installed.

Result:no show. :no:

The regsvr32 "C:\Program Files\Stardock\Object Desktop\WindowBlinds\wbui.dll" line now gives the following regsvr32 respond:

LoadLibrary(*C:\Program Files\Stardock\Object Desktop\WindowBlinds\wbui.dll") failed - Invalid access to memory . :angry:

What could it be? WB worked just fine on my former k6-2 450 with 3dfx v3k2, but now I've upgraded to an Athlon64 3500+ (Winchester) with GF 6600 PCIe it gives me the same symptoms as eRad describes in his posting (no wb option in display propeties--> appearence tab, no taskbar skining, nor windows (only in per application settings).

Btw: Using WinXP Pro (English) sp2 with WB 4.4.

What to do now, surely I shouldn't have to re-install windows for WB???

Well I'll be damned...

Just when I was about to re-install the whole XP

I checked the C:\Program Files\Stardock\Object Desktop\WindowBlinds

and clicked wbconfig.exe...and voila! WB works perfect. :blink:

Now, I still don't understand the 'why'of it.

WB option still doesn't appear in display propeties--> appearence tab,

and I haven't checked yet if the skin stays when I reboot XP (I'm in the middle of a delicate download you see), but this is great!!!! :woot:

@eRad: maybe you should try this too, because I had the same symptoms as you and this worked for me as you see.

Seriously I have never seen this type of problem before. Usually typing in the "regsvr32 "C:\Program Files\Stardock\Object Desktop\WindowBlinds\wbui.dll" works.....but I haven't seen it to the degree you are talking about.

Have you upgraded to the latest build of WB?

Definately contact Frogboy about this one.

Seriously I have never seen this type of problem before.? Usually typing in the "regsvr32 "C:\Program Files\Stardock\Object Desktop\WindowBlinds\wbui.dll" works.....but I haven't seen it to the degree you are talking about.

I keep gettingLoadLibrary(*C:\Program Files\Stardock\Object Desktop\WindowBlinds\wbui.dll") failed - Invalid access to memory> with that line andregsvr32>...

Have you upgraded to the latest build of WB?

I think so; WB: build 163 is installed.

Definately contact Frogboy about this one.

585204795[/snapback]

I will. I'm seriously considering re-installing WinXP... :crazy::

If anyone knows a better solution, please be so kind to enlighten me ;))

System specs:

Athlon64 3500+ (winchester)

Gigabyte K8 Tritron (GA-K8NF-9)

Geforce 6600 (256 mb/ PCIe)

1024 mb memory (DDR400 dual channel)

WinXP pro sp2 (English/slipstreamed; >worked fine with this WB build on my former pc,

which was a k6-2 450 mhz with a 3dfx v3k2>

Edit>

Following message sent to SD's Frogboy:

AthleticTrainer1981 advised me to inform you of this WindowBlinds skinning problem some of us are experiancing.   

Do you know what to do? 

Is it a familiar problem? Any solution? (besides re-installing WindowsXP???)   

I'd appriciate your advise beforehand.   

Respect,    Wiebeest     

Edited by wiebeest
I think so; WB: build 163 is installed.

I will. I'm seriously considering re-installing WinXP...  :crazy:

If anyone knows a better solution, please be so kind to enlighten me  ;)

System specs:

Athlon64 3500+ (winchester)

Gigabyte K8 Tritron (GA-K8NF-9)

Geforce 6600 (256 mb/ PCIe)

1024 mb memory (DDR400 dual channel)

WinXP pro sp2 (English/slipstreamed;

worked fine with this WB build on my former pc,

which was a k6-2 450 mhz with a 3dfx v3k2

Edit

Following message sent to SD's Frogboy:

585209394[/snapback]

Sorry I haven't been around, got back into town REAL early this morning, the newest build of WB is ver 4.49 build 177, so you should grab that new build off of stardock central. When you use SDC to update, it packs up the old install and installs the new version, it may take care of the problem.

update: it probably involves a known amd64/winxp sp2 problem mentioned here.

The latest build from Stardock seems to fix it,

I've d/l and installed & it worked!!!

Damnnit I am so tired I didn't even read your next post. The newest build did fix the problem. Good to hear that.

The newest build did fix the problem.  Good to hear that.

585211183[/snapback]

Yeah. Also I've read on these and other forums that the combination of Athlon64 processors and winxp sp2 (DEP) together with Windowblinds (amongst other apps) is not a lucky one. Windowblinds has been fixed in the newest stardock updates, in order to re-enable other apps people will have to disable DEP totally via:

system --> advanced --> startup and recovery settings--> edit bootloader:

"[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptIn"

Change noexecute/i] to execute, than save & reboot.

That should fix it

;)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Anybody that thinks flying cars were possible are idiots. Everyone would basically need a pilot licence, can you imagine how insane and dangerous that would be, people can barely handle driving on land safely right now.
    • Microsoft Edge 149.0.4022.80 by Razvan Serea Microsoft Edge is a super fast and secure web browser from Microsoft. It works on almost any device, including PCs, iPhones and Androids. It keeps you safe online, protects your privacy, and lets you browse the web quickly. You can even use it on all your devices and keep your browsing history and favorites synced up. Built on the same technology as Chrome, Microsoft Edge has additional built-in features like Startup boost and Sleeping tabs, which boost your browsing experience with world class performance and speed that are optimized to work best with Windows. Microsoft Edge security and privacy features such as Microsoft Defender SmartScreen, Password Monitor, InPrivate search, and Kids Mode help keep you and your loved ones protected and secure online. Microsoft Edge has features to keep both you and your family protected. Enable content filters and access activity reports with your Microsoft Family Safety account and experience a kid-friendly web with Kids Mode. The new Microsoft Edge is now compatible with your favorite extensions, so it’s easy to personalize your browsing experience. Microsoft Edge 149.0.4022.80 changelog: Fixes Fixed an issue that prevented QR code generation from working. Feature updates Intune MAM Protected Downloads. The protected downloads feature for Intune MAM will now save downloaded files to the Documents > Microsoft Edge > Downloads folder in OneDrive. Extensions monitoring in the Edge management service. The Microsoft Edge management service now allows admins to gain visibility into extensions installed across their managed users. From the extensions monitoring page, admins can see which extensions have been installed as well as manage user requests for blocked extensions. For more information, see Microsoft Edge Extensions Monitoring. Validate Edge builds early with enterprise preview. Enterprise preview provides a simpler way for admins to flight pre-release Edge builds to their users. To reduce friction and bolster usage, users will receive pre-release builds directly inside of their Stable Edge application. Admins can allow users to easily opt-out of the preview experience, using built-in rollback to switch between their pre-release and stable channels with ease. Microsoft 365 admin center users can configure the feature, view their flighting population, and receive personalized recommendations all in one place. For more information, see Get started with Enterprise Preview in Microsoft Edge. Download: Microsoft Edge (64-bit) | 193.0 MB (Freeware) Download: Microsoft Edge (32-bit) | 170.0 MB Download: Microsoft Edge (ARM64) | 188.0 MB View: Microsoft Edge Website | Release History Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!