Kevin, good to hear from you 
As you maybe know already, I was a little bit worried about the support for - , and the problems with 4.23 . It is good too see that you take them serious
I understand that you are very busy, but don’t you know someone who is very well into BOClean and who could be ( And ofcource want to be ) an Expert Moderator for the first line of support on the forum ??? As I understand it, Tony refused due to a lack of time 
Greetz, Red.
Great post. Thank you very much, you have answered my questions and made me happy. (:KWL)
You can include me in with the concern/worries for support.
You and Nancy gave top notch support and that loyalty was something very close to the customers of BOC.
Now that things have changed and you’re probably busy as hell at the moment hopefully this part of BOC wont change and will be just like before.
Hi Kevin,
Have had BOClean on my machine more years than I can recall and never had a problem until today.
Was suggested that I forwared this link for you to review:
https://forums.comodo.com/index.php/topic,8920.0.html
Might add that I opened the BOC423 file, and this was what was shown. Only changes I made was to remove my name and substitute * for my user name. Had been running BOClean on Vista and was getting daily updates until today.
[Prefs]
FileLoc=G:\PROGRA~1\Comodo\CBOClean
update=0
dataLoc=G:\ProgramData\BOC423\BOC423.XVU
sweeps=0
startscrn=1
NThook=*
Hung=
CRC128=F88C
FIXEDlast=ÀO³³ÎÏØj6æ²ÂRÇ
CRC128 FAILED=F00CF00C00128
[Updater]
final=G:\Users*\AppData\Local\Temp\BOC423.XVU
temp=G:\Users*\AppData\Local\Temp\BOC423.XVU
Vers=4.23.001
Date=04/08/07
Ops=have latest
Closed=Yes
[StartDel]
final=G:\Users*\AppData\Local\Temp\BOC423.XVU
Yes have been having a nuisance with an Error screen saying "Problem with getting an update. Although I have the latest version, and if you go in manually and tell it to check for an update it will do it and no Error. Other than that no problems, have been running BOClean for a few years now. Sorry I would have used a cute little Smiley face but none of them are holding a sign saying BOClean Rocks or anything like that. Although with the exception of the Comodo AntiSpam program the Code writers seem to be really quick with coming back with suggestions. Hope things work out in your new digs.
Now I know this is mainly for compatibility issues… But will I be able to choose a set time (Like… 12 o clock every day) for auto-updates? Instead of a period after bootup?
I’m having the connectivity problem. Keeps disconnecting my wireless. Is there a solution?
4.23 was running nicely overall. Only problem I had was with auto-updating, sometimes I get a error. So for now I uninstalled it, but I’ll try the new version for sure.
More people should work on stability and compatability instead of putting all sorts of bloat features in it.
Keep up the good work Kevin 
Kevin,
I’m having some problems with Excluder… https://forums.comodo.com/index.php/topic,8840.msg65252.html#msg65252.
LM
PS: Tnx, ~cat~ I knew I forgot something…
Would it make sense to split the “issues” out of this thread and create a “bug” thread apart from the announcement ?
Nope … I’d really appreciate this thread going the way it is. I don’t have much in the way of “free time” to come out and play here until 4.24 is done, and having indicated that 4.24 is my highest priority I’m really interested in knowing what needs to be fixed for 4.24 and having it all in one thread would be a tremendous help in getting that to happen in a timely fashion as I don’t have time to go through all the other threads at the moment.
It seems that there are a number of people suffering update problems and what’s truly strange there is that absolutely nothing in the updater code has changed (we’ve changed the version number but that’s about it) other than pointing the updates to the COMODO site instead of the NSClean site in 4.23 … that’s the ONLY difference. So it would appear that I need to dig into the possibility of some issues with the COMODO ftp server … any details on what people are seeing would be appreciated along with WHICH firewall you’re using. I can’t fathom how anything in the updater would affect a connection or lose same so I’m mystified here to say the least …
What I’m planning to do early next week once I have a “test build” of 4.24 done is to IM some of the affected people willing to test it and get them this “advance build” to play with and see if we’ve got those fixed. Still working on it though, and still interested in hearing a bit more. I may also have some people run a special diagnostic tool of ours to try to zero in on the culprits. That too is still in the works.
But for now, I’m VERY interested in knowing what problems exist that I’m not aware of so we can get those fixed in the code as well, so please carry on everyone - will try to follow links to otherongoing things but it’d really help me a lot if they’re posted in this thread.
Finally, THANKS everyone who was with us under PSC - COMODO indeed does intend to carry on the commitment PSC had with BOClean, it’s just been a challenge folding a “small company” into a bigger one - but we’re getting there … and the benefits of more hands to help out has already shown signs of great improvements “behind the scenes” … this will all be really worth it and signs of it will be apparent very soon!
Just out of curiosity, I haven’t had an update for several days. I use manual update. It simply connects, waits for a few seconds, then disconnects. I didn’t give it much thought, until someone mentioned ‘daily updates?’
Yep … sounds like we’ve either got a problem connecting to COMODO’s servers or everyone has some “security software” in common. So for everyone who is reporting “corrupted download” problems, I’d be quite curious as to what you’re using for a firewall and what other “security software” you’re running. I’m hoping we can pin down ONE program here, that’d confirm that it’s the program rather than a problem with the COMODO ftp server (not my yob, man) …
But what I’m PARTICULARLY interested in for the 4.24 release is those whose winsock stack got hosed after a trojan was detected - tells me that we’ve got a “bad actor” in the midst since all the BOClean “winsock repair” does is go through the stack and remove any “dead entries” which will occur after a winsock LSP hijacker has been removed. If any such program is yanked without “reconfiguring the winsock to remove the entry” then you lose connectivity. What I’m guessing is that some other program is doing something squirrely in there and those of you who have gone through that are the ones I’ll want to get in touch with in order to get a “snapshot” of your winsock stack with whatever is breaking it on the rebuild present there so I can see what they’re doing. This one is the most critical one for me with the 4.24 code - knowing what’s misbehaving and either working around it or detecting its presence and automatically shutting off the winsock repair if found.
As far as nuking the HOSTS file and clearing out the “zones settings” there is no way in creation to know which entries are real and which aren’t and so the only solution for cleaning those is to restore those entries to “Windows was just reinstalled” status. And “backing up what’s there” is not an option either because how would BOClean know if any entries were already hijacked or not? There’s a dilemma here logistically and as much as we’ve always tried to build “clairvoyance” into our code, Houdini has STILL not yet risen from the dead, though he’s been exhumed.
But the “complete loss of connectivity” until the system has been restored or reloaded … that’s a complete showstopper in my book. Bad updates is likely not the result of BOClean but something else. And yeah, that will get fixed too once identified as to the cause but nothing I can code into BOClean will solve that.
For those concerned about “always on top” for the BOClean traybar menu and the config screen - already fixed, as well as a few other items I don’t remember at the moment from lack of sleep.
For what it’s worth, I got updates, just after release, nothing since. As you might expect, CFP, but nothing else. As I said, it connects, waits a few seconds, disconnects. Is there a log for this…hmmm let me go see…
On most days, there’s typically two. Sometimes three updates in a day. That’s why the default of autoupdate every 6 hours, it was the right number. It’s looking more and more as though there might be some traffic problems with the COMODO server. One of the things we learned over the years with nsclean.com was that every couple of months the past year and change, we had to keep ordering up more and more bandwidth to prevent that and that was one of the costs that helped to put PSC under.
But for the moment, before I go rattling COMODO cages, I’d like to see if these have a particular firewall in common. If there’s different ones, that’ll be enough to make me go talk to a few people in the server farm and pull some chain. But I need some answers from a few people to figure out what we’ve got. DEFINITELY isn’t a BOClean problem or folks with 4.22 and earlier would have suffered the same.
The “blank windows” thing is interesting indeed … in order to keep the code compact and as swift as possible, our stuff isn’t checking every other clock cycle to see if a window needs to be redrawn, that’s what’s causing that - we’re not looking to “repaint” when the code is busy and it won’t “repaint” the window until it’s done doing what it’s doing.
However … normally, unless you pull up another window which covers ours, that just won’t happen unless some OTHER program is “stealing our focus.” Whatever’s going on here is definitely some natty actions of another vendor’s “security” program which is somehow nulling OUR window so they can peek inside what we’re doing. I’ve promised Melih to not be so blunt as I used to be when it was Nancy and I - I could say ANYTHING I felt whether people liked it or not because it was the TRUTH and that’s all Nancy ever expected from me. I have to be a bit more “diplomatic” now and thus, with this thread, I’ll let others post what they’ve got so we can see if it comes down to one single commonality. And I won’t be surprised to see who it is, but I won’t say anything just yet. I’d rather others speak, then it won’t be MY fault. Heh.
But yes, if you cover a BOClean screen with something else and then close it, we won’t redraw screens until we’re done with what we’re doing and back sitting in the WinAPI “message loop” waiting for the magic “WM_PAINT” to come along. When BOClean’s busy, “windows messages” are ignored since that’s always been a PRIME method of preventing “anti-whatever” software from detecting malware. So we cut off that method whilst busy.
So … (and this goes for all here) … “Whatcha running?” Windows version, firewall, anti-whatever-type “security software” … gots to be something in common here!
About the updates. There was some discussion about the host, it seems to be the Planet?
In CFP I have tried both rules, and just now, allow all, same. seems updates are not working for some…
If it’s COMODO firewall that’s the culprit, that’ll be EASY! Buy Egemen a ■■■■ … slap him a few times, share a joke, stroll into Melih’s office and PANTS him and we can both put our arms around each other and hide in the onion cellar! If it’s CPF, then it’s an EASY fix! Somehow though, I expect other “we’re the ONLY security software you need” vendor that’s behind it … by ALL means! If it’s a COMODO problem, it can be fixed once we can figure out what it is … if it’s another vendor’s problem, then I can get my guys to call it MALWARE and we’ll delete the sum’beech! Booowahahaha!
Nah … j/k … but we do need to figure out the hoser and fix it if we can …
Genuinely don’t know WHERE COMODO is hosting the updates, been too busy to care. I know COMODO is for real, where their space is rented - dunno. NSClean.com was hosted in Schenectady NY on logical.net and the demands of BOClean presented continuing challenges to them which they’ve ALWATS met for us by expanding the bandwidth, building special servers JUST for the BOClean updates from nsclean, and ensuring that our need for “PASV FTP using the DEFAULTS for Aiyee (IE)” just always worked. When MORE bandwidth was needed as the BOClean “family” expanded, the folks at logical.net SAW the traffic numbers and just adjusted as it grew and thus it was never anything in OUR faces, the logical.net folks just handled it silently and kept it all cool.
I’m being lead to believe that there’s possibly a problem with the COMODO servers, but I’d like to have a bit more evidence in order to bolster my argument if this is true … the more info folks can provide, the better my chances of launching “the fickle finger of fate.” =)
Now that Toggie mentions it …
Normaly I don’t have any problems, manual - and auto update seems to be working fine. But there where two times that I did a manual update and the same thing as with Toggie happened. It connected, waited a few seconds, and disconnected withought any message. So I thought there was maybe something with the ftp server. Because not much later BOClean was updated with auto update I thought it wasn’t worth mentioning it .
Greetz, Red.