Recommended Posts

That depends on the item.

Large items like a TV box I will keep till next bin day. (It scares me that people just put the whole box next to the bin as a giant invitation to thieves)

Small items like boxes for components for computer I will keep for about 6 months, If its shown no issues I don't see the point in keeping it any longer than that.

I keep them for a long time but only for reselling purposes. I find it's easier to sell something when you still have the original packaging. If it's something I know I won't sell, then I'll keep it until I clean out my basement.

So long it's embarrassing for some.

I was actually thinking I need to get rid of some of my old software boxes, too. It's not like I have a ton, I just pick random ones to hold on to. I'm pretty sure I still have a box from Command & Conquer: Tiberian Sun (released in 1999).

So long it's embarrassing for some.

I was actually thinking I need to get rid of some of my old software boxes, too. It's not like I have a ton, I just pick random ones to hold on to. I'm pretty sure I still have a box from Command & Conquer: Tiberian Sun (released in 1999).

ill raise u 1999 tiberian sun box to a 92/93 97 boxed copy of dune and dune 2 white label double pack still

  • Like 1

TV and larger items, until I'm satisfied I won't have to return a defective product. Other stuff like computer components, usually a few weeks, just in case something goes wrong. Boxes that can easily be re-used, I tend to keep for a while. I have a ton of shoe boxes in my closet, I use them for other stuff though, like pictures, dead batteries (until it's time to bring them to a battery recycling program), receipts, other smaller boxes, stuff that I don't really use very often, but often enough that I don't want to get rid of them.

Despite their size I keep boxes of cases and monitors. For transport original polystyrene packing is probably the best safeguard against anything less than a meteor impact. Older Samsung HDD plastic whatchacallits are useful for screws, adapters, cable ties and other little things. Other boxes aren't useful at all, but now that I look, I have kept embarrassingly most of them :pinch:

And then I also keep certain boxes for things I don't even have (GTX 690 being one, sad that I couldn't get hands on Titan's box)... just to keep me motivated, I guess :laugh:

Generally "until the warranty is up on the item" is my rule of thumb... but by then I forget about the box, so I just end up with boxes from ten years ago sitting around. I really should go clean some of that stuff out...

I have a rather nice process when it comes to keeping boxes, For consoles i keep them for the life of the product so that i can transport them in their original packaging, For the television I folded the box up to save on space and Kept it for as long as the warranty lasted. Small components I generally keep for 30 days (warranty or store return timeframe) and the same is for most thing, when the warranty is up the box can go.

Depends what it is.

Most boxes I keep in the loft. TV's, vacuum cleaner, food processor, camera, new monitor, window vac, kettle, meat mincer, iron... literally everything.

I do this because:

1) If and when I move house, it'll all go back in the original box to transport safely. Plus, when I unpack it again it'll be extra special rather than just getting it out a random box.

2) If I come to want to sell the item then I can sell it in the original box meaning more value.

The latter I have rarely, if ever done.

My parents loft is full of boxes which are 20+ years old. It's a time warp being in there. I also keep boxes which my cat food comes in as they are really heavy duty so will be good for moving. Luckily my loft has a lot of space!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • 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!