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. 



Tomorrow

Member
  • Content count

    383
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    1

Tomorrow last won the day on May 26 2014

Tomorrow had the most liked content!

Community Reputation

3 Neutral

About Tomorrow

  • Birthday 02/17/1986

Contact Methods

  • MSN
    tamma05@gmail.com

Profile Information

  • OS
    Windows 7 x64
  • Country
  1. Windows 7 SP1 is supported until January 14, 2020. Currently it is on extended support. We don't know what happens on January 15, 2020. Will MS extend support atleast one more time like they did with XP multiple times or not. I'm thinking they won't.
  2. That's a question to the developer although i imagine this has been discussed in MDL forums somewhere. Due to the bendwidth requirements i imagine most updates are coming from MS servers. Obviously this does not include updates that are request only (to fix a specific rare issue) and updates that are superseded but are kept around to satisfy WU.
  3. Frankly i don't really care if the list is encrypted or not. What i care is that it downloads current updates and removes superseded updates already on disk (i mean HDD not Win7 image). I admit it's not perfect tho. First the removal of superseded updates from disk takes several steps and the program itself has confusing UI. Plus the developer is a jerk (banned me from MDL forums for having the audacity to suggest improvements to his program). The list maintainers like abbodi and others are great tho.
  4. You fix this by not running an abandoned program. Use WTK instead: http://www.afterdawn.com/software/system_tools/system_tweaking/win_toolkit.cfm
  5. Move to NTFS formatted USB stick then. But yes it is a problem since on FAT32 install.wim cannot be larger than 4GB and thus one has to use other filesystems but booting install from those is not as easy as booting from FAT32 (and not as fast imo). Sorry for OT.
  6. Use Disk Cleanup. This removes superseded updates. Did you even read my post? How is a feature of an installed os relevant to the question i asked? What i wanted to see is something along the lines of this: Updates removed since december 2014 - march 2015 (for me at least) IE11-Windows6.1-KB2956283-x64 IE11-Windows6.1-KB3008923-x64 IE11-Windows6.1-KB3025390-x64 Windows6.1-KB2785220-x64 Windows6.1-KB2847311-x64 Windows6.1-KB2926765-x64 Windows6.1-KB2952664-v7-x64 Windows6.1-KB3002885-x64 Windows6.1-KB3013126-x64 Windows6.1-KB3013455-x64 Windows6.1-KB3023266-x64 Windows6.1-KB3023562-x64 Windows6.1-KB3029944-x64 I had a hunch some updates were obsolete by now, therefore after some googling on how to compare folder contents, found out that these ones are no longer relevant. Btw is there a website to check which updates were superseded, my google fu gave me irrelevant results. And once you find out what updates are superseded you do what? remove them one by one?. This is what disk cleanup is made for. It removes (among other things you select) superseded updates from the system. Essentially eliminating the quessing game about wich updates are superseded and wich are not. If you're talking about removing superseded update packages (.msu or .cab) from disk then that's another matter. Generally you're better offf deleting the previously downloaded files and redownloading the the nessesary updates each month. Trust me when i say that trying to figure out wich updates are currently superseded and keeping such a list updated is something many people have tried in the past (me included) and given up. It's a lot more complicated than you think. Often requiring extraction and examination of individual files inside the packages to deterimine if they're newer.
  7. Use Disk Cleanup. This removes superseded updates.
  8. Ask your Seven xml ? here

    Yes im pretty sure you can. Since i dont do this myself (no point in relocating user stuff from SSD with 90GB free to slower HDD) i cant offer any examples.
  9. Hmm. Seems RT7L is very much stuck in peoples mind. Unfortunately it's completely abandoned and unsupported. Using it will cause many issues. Use WTK instead: http://www.wincert.net/forum/files/file/5-win-toolkit/
  10. http://www.msfn.org/board/topic/139877-post-sp1-updates-for-windows-7-updated-13052014/page-18#entry1077997
  11. Ask your Seven xml ? here

    Hmm i see a hotfix coming : KB???????? - Windows setup creates ESP partition with incorrect size on advanced format (4K) drives on UEFI capable systems.
  12. Ask your Seven xml ? here

    Fsutil fsinfo ntfsinfo c: (Where C: is drive letter). If "Bytes per Sector" = 512 then: 512 If "Bytes per Sector" = 4096 then: 4K If "Bytes per Physical Sector" = 4096 then: 4K Emulated? Read up: http://support.microsoft.com/kb/2510009 My SSD is 512 wich explains why windows setup created 100MB partition not 260MB.
  13. Ask your Seven xml ? here

    Even windows installation itself creates a 100MB partition on SSD: Microsoft DiskPart version 6.1.7601Copyright (C) 1999-2008 Microsoft Corporation.On computer: PHOENIXDISKPART> list disk Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 59 GB 0 B * Disk 1 Online 698 GB 0 B * Disk 2 Online 2794 GB 0 B *DISKPART> select disk 0Disk 0 is now the selected disk.DISKPART> list part Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 System 100 MB 1024 KB Partition 2 Reserved 128 MB 101 MB Partition 3 Primary 29 GB 229 MB Partition 4 Primary 30 GB 29 GB
  14. Ask your Seven xml ? here

    Yeah i have always used 100MB ESP partition. Not sure why MS would suggest 200MB. Btw fixed code: <DiskConfiguration> <Disk wcm:action="add"> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Type>EFI</Type> <Size>100</Size> </CreatePartition> <CreatePartition wcm:action="add"> <Order>2</Order> <Type>MSR</Type> <Size>128</Size> </CreatePartition> <CreatePartition wcm:action="add"> <Order>3</Order> <Type>Primary</Type> <Extend>true</Extend> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Order>1</Order> <PartitionID>1</PartitionID> <Label>ESP</Label> <Format>NTFS</Format> </ModifyPartition> <ModifyPartition wcm:action="add"> <Order>2</Order> <PartitionID>2</PartitionID> <Label>MSR</Label> <Format>NTFS</Format> </ModifyPartition> <ModifyPartition wcm:action="add"> <Order>3</Order> <PartitionID>3</PartitionID> <Label>System</Label> <Letter>C</Letter> <Format>NTFS</Format> </ModifyPartition> </ModifyPartitions> </Disk> <WillShowUI>OnError</WillShowUI> </DiskConfiguration>
×