Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


bphlpt

Patron
  • Content Count

    2,261
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by bphlpt

  1. Hmmm. Sounds familiar, somehow. I hope the issues are not drastic enough to require this, but... Cheers and Regards
  2. I'm not that familiar with the inner workings of the Indexing Service, so I could be completely wrong, but I don't see this as an issue, especially since you're having problems with the Indexing Service anyway. If you really feel that using the MS Indexing Service is necessary for you, I'd be tempted to completely remove the Indexing Service, then be sure you have cleaned out any remnants of IIS, then reinstall the Indexing Service and let it re-Index everything. But I'd probably look at 3rd party alternatives to the MS Indexing Service instead of reinstalling the MS service. What aspects of the Indexing Service do you actually use? Many people look at the MS Indexing Service as something that takes up both space and CPU cycles that could be better used elsewhere and do not use it at all. Something to consider, but I would definitely get advice from someone who knows more about this than I do, such as jaclaz. Cheers and Regards
  3. But Powershell is not exactly a workstation only feature. Power user, yes, but not workstation, IMO. Powershell is just MS's next generation CMD language, and it isn't new by any definition. Cheers and Regards
  4. @Jody, click Dencorso's link above for KB3170735 to see what Woody says about it. Cheers and Regards
  5. Yes, there used to be a "Sent" box until very, very recently. Now, all conversations that are not drafts are put in the "Inbox", whether they have been responded to or not, In a way I guess that's actually more convenient. But now the name "Inbox" is no longer valid. Progress? As to why there are no longer pages 2, 3, etc, but just dynamically loaded "more", the pages are still there, which you will see if you let "more" load and then scroll through what is loaded. The "Page 2", etc, headings are still there. For the majority of folks this will not be an issue, but if you have a lot of messages, (such as xper?), I think this will be inconvenient. There is no reason I can think of why the ability to go directly to "Page 4" or whatever was removed. I think they tried to change the forum threads to this same navigation method , which would be totally unworkable for longer threads, so maybe the "Page" ability is still there and could be reinstated? Overall, it seems the IPB folks thought that the "Facebook" type model is appropriate for all forums? (I don't think that it is.) Cheers and Regards
  6. By the way, here is a complete list of all Windows 7 updates that should be excluded that i think would satisfy even the most paranoid. KB971033 KB2882822 KB2902907 KB2922324 KB2952664 KB2976978 KB2977759 KB2990214 KB2999226 KB3012973 KB3014460 KB3015249 KB3021917 KB3022345 KB3035583 KB3042058 KB3044374 KB3046480 KB3050265 KB3058168 KB3064683 KB3065987 KB3065988 KB3068708 KB3072318 KB3074677 KB3075249 KB3075851 KB3075853 KB3080149 KB3081437 KB3081454 KB3081954 KB3083324 KB3083325 KB3083710 KB3083711 KB3086255 KB3088195 KB3090045 KB3093983 KB3102810 KB3102812 KB3112336 KB3112343 KB3118401 KB3123862 KB3135445 KB3135449 KB3138612 KB3138615 KB3139929 KB3146449 KB3150513 This includes everything in Dencorso's current list of what to exclude to prevent being updated to Windows 10 against your will, along with additional updates that Yzowl feels are important to prevent sharing anything with MS. This list is current as of the May updates. I don't know for sure if either of them thought that there are any updates from the June list that should also be excluded or not. The update that fixes the MU/WU delay, KB3161608, comes to mind. Some might not want it, I don't know. Cheers and Regards
  7. If you're trying to install Windows 7, then no. Leave everything where it is. If you use abbodi1406's installer script, which you can find here - http://forums.mydigitallife.info/threads/44645-WHDownloader-Support-and-chat/page259?p=1169513#post1169513 - it will get what it needs from the correct folder. You have two methods you can choose: A) Use the convenience update, (which I didn't think you wanted to do), in which case use "WHD-W7UI.cmd" which will ignore everything in the "Extra\WithoutKB3125574" folder. B) Install the classic way, (which was what I thought the whole purpose of this project was), and use "WHD-W7UI_WithoutKB3125574.cmd" which will pull from "Extra\WithoutKB3125574" as it needs to. You can read both scripts to see exactly what they do, they're just batch commands. Basically, you are correct that without KB3125574 it will use the updates in both "Windows7-x64\Security" plus "Windows7-x64\Extra\WithoutKB3125574\#Security" etc. Everything in "Extra\WithoutKB3125574" is what is included in KB3125574, but since you're not going to use KB3125574 then you'll have to include those updates. Remember, there are still various telemetry updates scattered about which you might or might not want to include in your project. Whatever you don't want to include, simply move that update out of the regular location into somewhere that the install script won't pick it up. On my last install I left everything where it was and just did not select the option to install WAT and Windows 10 related updates, only about 7 in total if I remember right. Your project might appeal to more people and be more flexible if you also remove the telemetry updates. They can always be installed later if they are wanted/needed. I thought your project's intention was to basically do the same thing as the installer script, but instead of installing the updates, they would be combined into a single "rollup" that could be more easily installed by the end user. In any case, I thought the installer script would be a good staring point for you. You will also have to discover any additional updates that WUI/MU finds after you boot your installed system. I was surprised how many updates were found, but it was nowhere near the number that would have been found without the help of WHDownloader and the install script. Remember, using WHDownloader includes most of the "request only" hotfixes that you would have had to search for manually otherwise. I'm glad you have had good success downloading the updates using WHDownloader. It was quick and easy, wasn't it? Cheers and Regards
  8. We can't do it that way here. Using WHDownloader is fine because the user ends up downloading all of the updates themselves directly from Microsoft. I'm curious how far along you have gotten downloading the updates with your described method over the last two and a half weeks? And why you have not tried actually using WHDownloader yet? I ask because I just downloaded a fresh copy of WHDownloader, put it in an empty folder, D:\WHD, downloaded a fresh copy of the download lists, selected the Windows 7 x64 list. selected all available updates, and clicked download. Downloading all of the updates was completely automated and took about a half an hour. I then selected the Windows 7 x86 list, selected all available updates, and clicked download. Downloading all of the updates took less than half an hour. The end result is D:\WHD having 1281 files in it, taking up 5,841,899,614 bytes. The updates are all named correctly (ending in either -x64 or -x86), the files are stored in x64 and x84 folders, and within those folders the updates are sorted into various categories such as General. Hotfix, Security, Extra, Additional, etc, along with text files that explain what some of the different categories are for. What took the longest to download was the convenience updates because of their size, and maybe because of the demand for them, I don't know. I don't plan on using them, but I went ahead and downloaded them just to have a complete set of updates. If you don't want any particular updates then don't select them and downloading will be quicker and will take less space. Once you have downloaded the updates one month, when the lists are updated the next month the only things that are downloaded are what is new or missing, taking much, much less time. You can download updates en mass like I did or one at a time if you prefer. It all depends on what you select before you click download. If, like me, you couldn't figure out where to get the download lists, here's the trick. When you run WHDownloader.exe, click the little box in the upper left corner. That's it, it will download all of the available lists and you can select the one you want to use in the pull-down. TRY IT! Let us know if you have any problems. If you are unwilling to use WHDownloader, or one of the other available download tools, then I'm really curious as to why. And if you haven't gotten very far in downloading updates over the last two and a half weeks, then I'm concerned about your true intentions. I can understand that you're busy with other things, but ... I have no problem at all in helping you, but besides being against MSFN policies, it would take far longer to zip and upload the updates and you to download them, than for you to just download them yourself using my above described method. Good luck with your project and I truly hope you are able to complete it. Cheers and Regards
  9. The problem is that KB3161647 is not available by itself, but only as part of KB3161608, which from all reports does fix the endless wait times to update Windows 7 - at least this month. There are no GWX components to KB3161608, but there might be some minor telemetry aspects in it ( I have heard that it includes KB3138612 but I'm not sure if that's true). So you have to decide if it's worth it, or maybe wait until next month and see if it still fixes the issue or if there is another "solution". Cheers and Regards
  10. I know it's a little OT, but how much of this is also applicable to Windows 7, or is there a current Windows 7 version of this guide? Cheers and Regards
  11. bphlpt

    No Updates!

    Are there any things in KB3161608 that those of us who are choosing to hide updates might not want? ie, is it "safe" tp install KB3161608 as is, or do we need to extract only the Windows Update Agent pieces of it? Cheers and Regards
  12. Just FYI, I was able to download the complete WHDownloader available hotfix selections in about 30-45 minutes, IIRC. And the hotfix's able to be downloaded are not impacted by what is installed on your system. WHDownloader on its own is a downloader, not an installer. So personally, based on my good experiences with the downloading ability of WHDownloader, I would suggest doing things the other way around than what you have proposed. I'd let WHDownloader get everything it can, all automated, then get the rest of the updates you need in the manner you outlined. But that's just me. Cheers and Regards
  13. You might want to check out WHDownloader - http://forums.mydigitallife.info/threads/66243-WHDownloader-Download - and the WHD list maintained by abbodi1406 referenced here - http://forums.mydigitallife.info/threads/44645-WHDownloader-Support-and-chat/page259?p=1169513#post1169513. I did a Windows 7 Ultimate x64 installation a couple of weeks ago starting with a MSDN SP1 source then used those tools along with abbodi1406's updates installer script to begin the update process. I also did not like the idea of using the "convenience" rollup for the same reasons you don't. I chose to install all the updates I could find except language packs, WAT, and Windows 10 related. Even after using abbodi1406's script MU/WU still found many more updates available, but it was a wonderful starting point. ( I currently have 657 updates installed. ) The WHDownloader will download the updates in the lists very, very quickly, and then you can use whatever method you chose to install them. It would be great if you are able to figure out how to create a rolllup from them, since the installation process using abbodi1406's script and then WU/MU takes a long, long time, several hours altogether. The rollup would also end up taking less installed space and be easier to deal with - all the advantages that MS touts for its existing convenience rollup. Good luck in your project! Cheers and Regards
  14. bphlpt

    Windows updates

    I'm guessing he meant Windows Updates Downloader? - http://www.windowsupdatesdownloader.com/ [ Which is an alternative to Windows Hotfix Downloader - http://www.majorgeeks.com/files/details/windows_hotfix_downloader.html or http://forums.mydigitallife.info/forums/56-WHDownloader ] Cheers and Regards
  15. To bring whoever cares up to date, whatever the problem was, it appears the problem was indeed on my end. After a fresh install of Windows 7 Ultimate x64, completely up to date, hiding only language packs, WAT, and Windows 10 related "updates", (WU/MU now showing a total of 657 updates installed LOL ), I no longer have any problems with any version of Chrome that I can find. I have most recently tested: Chromium v38.0.2081.0 x86 portable - this version has always worked Chromium v53.0.2763.0 x86 - true PortableApp Chromodo v50.14.22.468 x86 portable COMODO Dragon v50.14.22.465 x86 portable Google Chrome v51.0.2704.63 x86 portable Google Chrome v51.0.2704.63 x64 portable Google Chrome v51.0.2704.103 x64 - "regular" install Yandex v16.6.1.30051.beta Slimjet v10.0.5.0 x86 portable Slimjet v10.0.5.0 x64 portable SRWareIron v51.0.2700.0 x86 portable SRWareIron v51.0.2700.0 x64 portable It ended up that I was having problems with the newest version of Opera after all, but no longer. These now work: Opera v38.0.2220.31 portable Opera beta v39.0.2256.4 portable while the older versions of Opera have always worked: Opera Next v23.0.1522.28 portable Opera 12.18 portable Opera 12.18 x64 portable I've also tested other browsers including Brave, Ice Dragon, Maxthon, Firefox, Pale Moon, Safari, Vivaldi, Otter, K-Meleon, Cyberfox, Waterfox, Sea Monkey, and of course IE, all the latest versions I could find, both x86 and x64 versions if available and if they would both install and be able to run though the Firefox versions would usually not both run at the same time, and portable where I could find them. So I think I can put this issue to bed, whatever it was. Cheers and Regards
  16. I meant the folder where Thunderbird is installed, in Program Files or wherever you have it. As to the "folders that you created", assuming you mean the Local Folders, yes those have always been left alone, but I have those in a separate location and they are separately backed up as well. You could also use a portable version of Thunderbird, which might be easier to back up, for peace of mind. Cheers and Regards
  17. I don't have the issue with any version of Opera, from 12 to the newest, only Chrome. But I'm about to start my OS reinstall. Once done, I'll see if the problem still exists. If not, then I'll assume it was just something I messed up in the last install somehow. If it is still there, then we'll investigate further. Cheers and Regards
  18. I've updated the version on my wife's Windows 7 computer several times and it hasn't lost an email yet. But I've always saved a copy of the current install folder "just in case". Cheers and Regards
  19. Thanks for responding. I tried my tests with Chrome, Chromium, COMODO Dragon, SRWare Iron, and Yandex, both the x86 and x64 versions where available, all products of the same foundation, ie Chrome, and the results were the same for all of them. All seem to work fine, EXCEPT when I open the settings page, and only when I open the settings page, they cause a Windows error box to open saying "(the application) has stopped working" and the browser closes when the error box is closed. And it's not leftover stuff from a previous installation of the app since this happens with a fresh install after I cleanly reinstalled my OS. But I'll be reinstalling my OS again this weekend and hopefully the problem will resolve itself. Cheers and Regards
  20. Might be something weird with my install, then. I'm getting a new motherboard tomorrow and will be reinstalling. I'll post back whether or not I still have the issue. Thanks anyway for checking and the suggestions. Cheers and Regards
  21. Thanks guys. Yes I know that browser.exe is not a Windows file, but my point was that Windows was the one that opened the error box, and it wasn't the app that "crashed", at least not in the app's mind, ie no crash report is generated by the app itself. Anyway, I will be replacing my motherboard within the week and will be re-installing the OS again, so I'll start over and make sure that I know exactly what is or is not there, and why, and then see if the problem is still there. In the meantime, I'll be glad to run any tests anyone can think of to verify what the issue is, to make sure I don't inadvertently recreate the problem. Cheers and Regards
  22. Thanks Trip, but KB3118401 didn't help. I agree with your thought process, but I can't for the life of me think what is special about the settings page of the later versions of Chrome to cause a Windows error. Hopefully someone will chime in with knowledge of an error log that might be generated, (and know how to read it), that might help identify the culprit, or point to what Windows thinks is missing, or whatever. At least the problem is reliably repeatable so I can make it occur on command. Cheers and Regards
  23. Just thought I'd throw this out there on the off chance that maybe it's related to one of the updates I've hidden. [Den, if you feel this should be moved to a different or new thread, feel free to relocate it, but since I think the root cause is a Window's issue, maybe you'll agree it should be here, at least until the root cause is found.] I typically stick with programs, and OS, that work for me and only update things occasionally or when I really have to. I had to reinstall my OS which prompted me to update my programs while I was at it. I've noticed that on my Windows 7 x64 Ultimate system, where I have hidden all of the Windows 7 updates listed in the first post but is otherwise up to date, that I have a peculiar situation when trying to use any of the Chrome variant browsers, ie Chrome, Chromium, COMODO Dragon, SRWare Iron, Yandex, etc. All "older", ie older than about 3 or 4 months ago or so, versions of all of those browsers work perfectly fine. But when I use one of the newer versions, and some of them update automatically so I don't have a choice, they also seem to work fine, EXCEPT the browser crashes when I open the browser's "settings" page. Actually, the browser doesn't "crash", but rather it immediately opens a Windows generated error box saying, (with Yandex for example), "Yandex has stopped working" with the following details: ---------------------------------------------------- Problem signature: Problem Event Name: BEX Application Name: browser.exe Application Version: 50.0.2661.6376 Application Timestamp: 57213418 Fault Module Name: browser.dll Fault Module Version: 50.0.2661.6376 Fault Module Timestamp: 5721274e Exception Offset: 00eaaf56 Exception Code: c0000409 Exception Data: 00000000 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: c5e6 Additional Information 2: c5e64b3b479b160ea66cecb9ccafe654 Additional Information 3: 4b11 Additional Information 4: 4b11d7ebaa978fc34a59f011dc3a763f Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt ----------------------------------------------------- No error log is created by the various browsers. To them, when you try to reopen them, it is just as if they were shut down improperly, that's all they know. And no other running process is effected, that I've been able to tell. So it's Windows that is shutting things down, but it is ONLY for recent versions of Chrome, and ONLY when opening the settings page, which seems to point to a Chrome problem, at least to me. I've submitted the bug to Yandex, where I first saw it, but no luck so far. In Yandex's case, something changed between version 16.2.0.2586 beta and version 16.6.0.6376 beta. More info that might help is that in testing SRWare Iron, I found that: These versions all work fine with no crashes: v46.0.2450.0 v47.0.2500.0 v48.0.2550.0 v48.0.2550.2 These versions all work fine everywhere EXCEPT they crash when opening the settings page: v49.0.2600.0 v50.0.2650.0 And for all browsers that offer both x86 and x64 versions, the problem is exactly the same for both. I have noticed no other mysterious errors in any other programs I have run, so far, and yes, I could use Opera, or a Firefox related browser, or even "shudder" IE, but Chrome is my preferred browser and I'd like to fix this since I'm afraid it's just a symptom of a deeper problem. I'm not an expert on evaluating Windows OS errors, so I could use some help. Has anyone seen this behavior or do you have any suggestions of what I can try to fix, or at least better evaluate, this issue? I would be most appreciative. Cheers and Regards
×
×
  • Create New...