# Windows Server 2003 and FinalBuilder

**URL:** https://www.finalbuilder.com/forums/t/windows-server-2003-and-finalbuilder/714
**Category:** Discussion
**Created:** [January 14, 2008, 6:03am UTC](https://www.finalbuilder.com/forums/t/windows-server-2003-and-finalbuilder/714 "2008-01-14T06:03:49Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![deleted\_user](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/deleted_user/32/937_2.png) [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [January 14, 2008, 6:03am UTC](https://www.finalbuilder.com/forums/t/windows-server-2003-and-finalbuilder/714/1 "2008-01-14T06:03:49Z")

</div>

FinalBuilder doesn't seem to like Windows Server 2003 - it tells me that I must install one of the following .Net CLR versions:

&nbsp;3.5

I have 1.0, 2.0, 3.0 and 3.5 installed - and rebooted the box. FinalBuilder still can't seem to find the CLR.

I realize this has probably been covered but -- you try searching on "2003 Server CLR" :)

&nbsp;FYI:

&nbsp;Windows 2003 SP3 x86 32 bit  
&nbsp;English (US)  
&nbsp;

---

<div class="post-metadata">

### Author: ![deleted\_user](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/deleted_user/32/937_2.png) [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [January 14, 2008, 7:05am UTC](https://www.finalbuilder.com/forums/t/windows-server-2003-and-finalbuilder/714/2 "2008-01-14T07:05:22Z")

</div>

Never mind - set the CLR to 2.0 in FinalBuilder options as per [url=https://www.finalbuilder.com/forums.aspx?forumid=1&postid=5677&view=topic]this thread[/url].

&nbsp;

---

<div class="post-metadata">

### Author: ![angus](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/a/b3f665/32.png) [@angus](https://www.finalbuilder.com/forums/u/angus)
#### Post date: [January 14, 2008, 10:55am UTC](https://www.finalbuilder.com/forums/t/windows-server-2003-and-finalbuilder/714/3 "2008-01-14T10:55:56Z")

</div>

Thanks Oliver, glad you found a workaround. We should have an official release which completely fixes this problem, very soon.