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

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!